Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a54377656c73499244c2ef260cbf75838c3c116c2d7ab5f89f4b6873b1c6d41c

Tx prefix hash: 742b6674c1e2c77b1735dcbce9c4fca21c71d591f1a232fe6640441763de86e8
Tx public key: dc4dbca23c5ef0531759e7042ad2bd94a0a55b74cf947e7f357ba146a15f8e3d
Timestamp: 1709752035 Timestamp [UCT]: 2024-03-06 19:07:15 Age [y:d:h:m:s]: 01:068:11:57:33
Block: 972602 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 309978 RingCT/type: yes/0
Extra: 01dc4dbca23c5ef0531759e7042ad2bd94a0a55b74cf947e7f357ba146a15f8e3d02110000000652d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c438bdfee3d97a308651feacded23984081cd4abbbb328c09e0c5fd879c2361b 0.600000000000 1432519 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": 972612, "vin": [ { "gen": { "height": 972602 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c438bdfee3d97a308651feacded23984081cd4abbbb328c09e0c5fd879c2361b" } } ], "extra": [ 1, 220, 77, 188, 162, 60, 94, 240, 83, 23, 89, 231, 4, 42, 210, 189, 148, 160, 165, 91, 116, 207, 148, 126, 127, 53, 123, 161, 70, 161, 95, 142, 61, 2, 17, 0, 0, 0, 6, 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