Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d0c57328ebcb53b329472c61cd797675243bd154e94e73af315a1282552f110e

Tx prefix hash: 77bfcb367e0ff1e91789330d7f11cbd305750d74e584158bd4f0aa2f62649a66
Tx public key: c31ea809a3e83432fc0c1229ccc858efb446a04d4b0922f4f3d601a08fa493f1
Timestamp: 1737333184 Timestamp [UCT]: 2025-01-20 00:33:04 Age [y:d:h:m:s]: 00:149:15:29:24
Block: 1201061 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 106700 RingCT/type: yes/0
Extra: 01c31ea809a3e83432fc0c1229ccc858efb446a04d4b0922f4f3d601a08fa493f10211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c7c3d7141e614ad6aa9589cbace2e5b98a0d4473a7ada69c37eb4472c7519d38 0.600000000000 1687708 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": 1201071, "vin": [ { "gen": { "height": 1201061 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c7c3d7141e614ad6aa9589cbace2e5b98a0d4473a7ada69c37eb4472c7519d38" } } ], "extra": [ 1, 195, 30, 168, 9, 163, 232, 52, 50, 252, 12, 18, 41, 204, 200, 88, 239, 180, 70, 160, 77, 75, 9, 34, 244, 243, 214, 1, 160, 143, 164, 147, 241, 2, 17, 0, 0, 0, 5, 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