Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1ea1d62203b087b56509d2cfa937213142eb123f69b62d1e6417ddbdd612c846

Tx prefix hash: cbbf8b06540d18a35f7e672783d6836dd0c0dae8d21ee2d7208ff4eeddc236db
Tx public key: 0e5fcf235546fae55721374c12eee38c2a7e50f72f20fb1f828b725bd3057fea
Timestamp: 1713212276 Timestamp [UCT]: 2024-04-15 20:17:56 Age [y:d:h:m:s]: 01:234:15:15:33
Block: 1001260 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 426404 RingCT/type: yes/0
Extra: 010e5fcf235546fae55721374c12eee38c2a7e50f72f20fb1f828b725bd3057fea02110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6e45e7d01044dfc0470df7b6aae49edf76cf74d021cea3b0351e982b85beae00 0.600000000000 1461764 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": 1001270, "vin": [ { "gen": { "height": 1001260 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6e45e7d01044dfc0470df7b6aae49edf76cf74d021cea3b0351e982b85beae00" } } ], "extra": [ 1, 14, 95, 207, 35, 85, 70, 250, 229, 87, 33, 55, 76, 18, 238, 227, 140, 42, 126, 80, 247, 47, 32, 251, 31, 130, 139, 114, 91, 211, 5, 127, 234, 2, 17, 0, 0, 0, 2, 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