Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a002e37e3698c8d7046b5eadf88e7d4f42ef3c57fac605e72d3e2536f9de280f

Tx prefix hash: c2e3d349e82a047375959e6e0587a03f5f7d1b06fffcfd07c02fe04158cc36eb
Tx public key: d8a4699cd8cef03b6b165e4123105820526a0912f863052d3356b12ff80f7268
Timestamp: 1726746539 Timestamp [UCT]: 2024-09-19 11:48:59 Age [y:d:h:m:s]: 00:205:18:30:55
Block: 1113480 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 146893 RingCT/type: yes/0
Extra: 01d8a4699cd8cef03b6b165e4123105820526a0912f863052d3356b12ff80f726802110000000186b38f76000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: af0e2d7f4aad877221cbce23a6e9ed83e0cd0cd8c2d52dba1b243c3a53da64e3 0.600000000000 1593167 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": 1113490, "vin": [ { "gen": { "height": 1113480 } } ], "vout": [ { "amount": 600000000, "target": { "key": "af0e2d7f4aad877221cbce23a6e9ed83e0cd0cd8c2d52dba1b243c3a53da64e3" } } ], "extra": [ 1, 216, 164, 105, 156, 216, 206, 240, 59, 107, 22, 94, 65, 35, 16, 88, 32, 82, 106, 9, 18, 248, 99, 5, 45, 51, 86, 177, 47, 248, 15, 114, 104, 2, 17, 0, 0, 0, 1, 134, 179, 143, 118, 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