Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 51f97c2ae369dc430b4d707f6fafb6cf3afa9380be602c0c9c7bf7733a0d4595

Tx prefix hash: 5baeb0be72308c3715fa11f721da63156729d46e5cf2f4f398b732d7b6e24f51
Tx public key: c473ba9d82762c74dadd8e3827d4c1e84240decc870214468285a2c1a18d7146
Timestamp: 1736947723 Timestamp [UCT]: 2025-01-15 13:28:43 Age [y:d:h:m:s]: 00:341:14:22:43
Block: 1197914 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 241693 RingCT/type: yes/0
Extra: 01c473ba9d82762c74dadd8e3827d4c1e84240decc870214468285a2c1a18d71460211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2bd44919506c61eddb7cd4ebf96f751f3389fb937393d4d7d8a41c5317319a13 0.600000000000 1684531 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": 1197924, "vin": [ { "gen": { "height": 1197914 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2bd44919506c61eddb7cd4ebf96f751f3389fb937393d4d7d8a41c5317319a13" } } ], "extra": [ 1, 196, 115, 186, 157, 130, 118, 44, 116, 218, 221, 142, 56, 39, 212, 193, 232, 66, 64, 222, 204, 135, 2, 20, 70, 130, 133, 162, 193, 161, 141, 113, 70, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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