Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d1e3818896b650bc3d0a5dc4d2561d26363dbd17af8d2265dcda74d9cd82656c

Tx prefix hash: c8cc1b73e52da0128093d9f74ee5d5135fcff082341c50a17236f6745a405a5d
Tx public key: 0a2c4c8a68caeb7440ab4d0f3f61d8d92999a0c873aea3f1e301c6933ceaea80
Timestamp: 1704855534 Timestamp [UCT]: 2024-01-10 02:58:54 Age [y:d:h:m:s]: 01:301:19:08:48
Block: 931987 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 474513 RingCT/type: yes/0
Extra: 010a2c4c8a68caeb7440ab4d0f3f61d8d92999a0c873aea3f1e301c6933ceaea8002110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4df75d844c0974a0cc3027a714a31f403c3549c081545a28733f0c5fb39d66de 0.600000000000 1389899 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": 931997, "vin": [ { "gen": { "height": 931987 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4df75d844c0974a0cc3027a714a31f403c3549c081545a28733f0c5fb39d66de" } } ], "extra": [ 1, 10, 44, 76, 138, 104, 202, 235, 116, 64, 171, 77, 15, 63, 97, 216, 217, 41, 153, 160, 200, 115, 174, 163, 241, 227, 1, 198, 147, 60, 234, 234, 128, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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