Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: bd9710396bb876da08873bf920398cdbd7865cc1a1374383e66ad499ce9df2b0

Tx prefix hash: 6f1358fa34c8b97c1de32c1a6f2ec5575a01db4874fb08d93d925ef591f88bcd
Tx public key: ed6a73d1f82ba1575a46c8949e05a87caf34cf50f5f02d727348654f9182cda8
Timestamp: 1712671743 Timestamp [UCT]: 2024-04-09 14:09:03 Age [y:d:h:m:s]: 00:321:22:12:44
Block: 996774 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 230150 RingCT/type: yes/0
Extra: 01ed6a73d1f82ba1575a46c8949e05a87caf34cf50f5f02d727348654f9182cda80211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 355278923aee8e0a766b192b1775af51ce09ae57536d752d86dc56f26f45e5c0 0.600000000000 1457202 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 996784, "vin": [ { "gen": { "height": 996774 } } ], "vout": [ { "amount": 600000000, "target": { "key": "355278923aee8e0a766b192b1775af51ce09ae57536d752d86dc56f26f45e5c0" } } ], "extra": [ 1, 237, 106, 115, 209, 248, 43, 161, 87, 90, 70, 200, 148, 158, 5, 168, 124, 175, 52, 207, 80, 245, 240, 45, 114, 115, 72, 101, 79, 145, 130, 205, 168, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8