Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4ff08d6e05571cdeee237ef2fb65d8f55e02cad92760f3aa8e79e6d76601e45a

Tx prefix hash: 30c1d9c8a30ee80e6758bae57b21675befcc662b7b338ff6bf818141bb0a729b
Tx public key: ab767706d578a4abf4b7b57d30e9256fb2db3a42f72c655fb90d2942e2ef8965
Timestamp: 1719910092 Timestamp [UCT]: 2024-07-02 08:48:12 Age [y:d:h:m:s]: 00:294:08:57:12
Block: 1056809 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 210344 RingCT/type: yes/0
Extra: 01ab767706d578a4abf4b7b57d30e9256fb2db3a42f72c655fb90d2942e2ef896502110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9c3fedbf615488ae66b73d3e2fb309246707f2cfae56498ef4ef90e9d576e801 0.600000000000 1527238 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": 1056819, "vin": [ { "gen": { "height": 1056809 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9c3fedbf615488ae66b73d3e2fb309246707f2cfae56498ef4ef90e9d576e801" } } ], "extra": [ 1, 171, 118, 119, 6, 213, 120, 164, 171, 244, 183, 181, 125, 48, 233, 37, 111, 178, 219, 58, 66, 247, 44, 101, 95, 185, 13, 41, 66, 226, 239, 137, 101, 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