Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9d1ab7b10c3ff3efb891e14d2d65115a6a218f8731bbea87f0d347ed5af6e898

Tx prefix hash: 342fff1efdd2f994142d1b28b13e74b17a350de128fb98566172eeee7dc919f0
Tx public key: 3571f7b7c69ba30467b0d707a41de0ede946fd0ba156d69fbd30f8ffb57575c1
Timestamp: 1729141074 Timestamp [UCT]: 2024-10-17 04:57:54 Age [y:d:h:m:s]: 00:021:22:49:53
Block: 1133339 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 15641 RingCT/type: yes/0
Extra: 013571f7b7c69ba30467b0d707a41de0ede946fd0ba156d69fbd30f8ffb57575c102110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e9b8369ec713ae020b250c672bb1c25a4ea58f704fdc93f364d18bb573e6e7d3 0.600000000000 1616440 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": 1133349, "vin": [ { "gen": { "height": 1133339 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e9b8369ec713ae020b250c672bb1c25a4ea58f704fdc93f364d18bb573e6e7d3" } } ], "extra": [ 1, 53, 113, 247, 183, 198, 155, 163, 4, 103, 176, 215, 7, 164, 29, 224, 237, 233, 70, 253, 11, 161, 86, 214, 159, 189, 48, 248, 255, 181, 117, 117, 193, 2, 17, 0, 0, 0, 3, 145, 225, 60, 4, 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