Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1476c47349e1d9aabb3a27d80ab4f1a7873c13b63677ae5477bcc01d60cbaca2

Tx prefix hash: 29590de169f7a65d201ee3f8c7cd0f386167f61c64c095dd28a1bdfec8913c79
Tx public key: 7f83e50b08c969b4ea1e3c3c47860863257529f2b4322f978f2d4b13a8cb7684
Timestamp: 1717235837 Timestamp [UCT]: 2024-06-01 09:57:17 Age [y:d:h:m:s]: 00:352:11:11:29
Block: 1034648 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 251917 RingCT/type: yes/0
Extra: 017f83e50b08c969b4ea1e3c3c47860863257529f2b4322f978f2d4b13a8cb768402110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e4e54dc3a4a4d76cb8f0f87a2c1209a0bfb28e3a37456c5a4285313e4a8b2385 0.600000000000 1503163 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": 1034658, "vin": [ { "gen": { "height": 1034648 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e4e54dc3a4a4d76cb8f0f87a2c1209a0bfb28e3a37456c5a4285313e4a8b2385" } } ], "extra": [ 1, 127, 131, 229, 11, 8, 201, 105, 180, 234, 30, 60, 60, 71, 134, 8, 99, 37, 117, 41, 242, 180, 50, 47, 151, 143, 45, 75, 19, 168, 203, 118, 132, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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