Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c48fd32aa80ab0b42167f1da79227407cff3f09a2981f61c83a7cfefb167c3d4

Tx prefix hash: 71048e3bfdbcacc0df2d357ef612eb55e5732c48b0575e5b12d3030db35fb2a5
Tx public key: 93096210b0a8b0e22e10b691fe0ff1f5877ed59dd006cc5e58ad62405021948d
Timestamp: 1713739001 Timestamp [UCT]: 2024-04-21 22:36:41 Age [y:d:h:m:s]: 00:262:03:16:46
Block: 1005640 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 187643 RingCT/type: yes/0
Extra: 0193096210b0a8b0e22e10b691fe0ff1f5877ed59dd006cc5e58ad62405021948d0211000000067a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: af877fbc474f59d3dc366cbf1b0a46b58003ea224a0c9d206a841de1848910a3 0.600000000000 1466394 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": 1005650, "vin": [ { "gen": { "height": 1005640 } } ], "vout": [ { "amount": 600000000, "target": { "key": "af877fbc474f59d3dc366cbf1b0a46b58003ea224a0c9d206a841de1848910a3" } } ], "extra": [ 1, 147, 9, 98, 16, 176, 168, 176, 226, 46, 16, 182, 145, 254, 15, 241, 245, 135, 126, 213, 157, 208, 6, 204, 94, 88, 173, 98, 64, 80, 33, 148, 141, 2, 17, 0, 0, 0, 6, 122, 156, 244, 199, 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