Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4fecf126f87e73ed28aca0fa5bd0643716af1d45d522224b90170a0d30710f7c

Tx prefix hash: 35f8ce0ea7f6e16745c1217f8930d1ef5d4b048478ee4547e6d239ccf24e54f6
Tx public key: 6aa14c4c7e32e9af3576a18657719702c025b1f538539e8a518846338daeea31
Timestamp: 1704575479 Timestamp [UCT]: 2024-01-06 21:11:19 Age [y:d:h:m:s]: 01:308:10:26:20
Block: 929661 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 479276 RingCT/type: yes/0
Extra: 016aa14c4c7e32e9af3576a18657719702c025b1f538539e8a518846338daeea3102110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4b31bab6287a788b4b846d1420a0c6c764b91d879f776ff21f591db7901a2a63 0.600000000000 1387537 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": 929671, "vin": [ { "gen": { "height": 929661 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4b31bab6287a788b4b846d1420a0c6c764b91d879f776ff21f591db7901a2a63" } } ], "extra": [ 1, 106, 161, 76, 76, 126, 50, 233, 175, 53, 118, 161, 134, 87, 113, 151, 2, 192, 37, 177, 245, 56, 83, 158, 138, 81, 136, 70, 51, 141, 174, 234, 49, 2, 17, 0, 0, 0, 1, 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