Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c2e17a545f99881b8e9d4ae78562a0d2aedf0155a435366c9945a911c858b781

Tx prefix hash: 3e703cdbf97c3f97f83bd9c0d68ea5fd3a12cc0f1dfe56783b5701ef1bd30598
Tx public key: 29375860df85fbf39e64d1f5b5fe41c5ebe8ee2525ac22b37f16cdcc753690d7
Timestamp: 1745875042 Timestamp [UCT]: 2025-04-28 21:17:22 Age [y:d:h:m:s]: 00:205:07:31:48
Block: 1271561 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 144451 RingCT/type: yes/0
Extra: 0129375860df85fbf39e64d1f5b5fe41c5ebe8ee2525ac22b37f16cdcc753690d702110000000a9f9fe68c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 13f0403ef3d1f3d147710106bc8bae37b21fbe86d34fa7ae921223803b92cadc 0.600000000000 1758824 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": 1271571, "vin": [ { "gen": { "height": 1271561 } } ], "vout": [ { "amount": 600000000, "target": { "key": "13f0403ef3d1f3d147710106bc8bae37b21fbe86d34fa7ae921223803b92cadc" } } ], "extra": [ 1, 41, 55, 88, 96, 223, 133, 251, 243, 158, 100, 209, 245, 181, 254, 65, 197, 235, 232, 238, 37, 37, 172, 34, 179, 127, 22, 205, 204, 117, 54, 144, 215, 2, 17, 0, 0, 0, 10, 159, 159, 230, 140, 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