Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4aa0ba115bad2d6a4dd975679eaeef35e0c3d745e039a574aac441d0a7495044

Tx prefix hash: 873a9e2cf53257c90458b38e9dfd113a74e81c34d82764392ffc7bc649714628
Tx public key: 5e89ce24620155c51df5e407dd665c7ae56fc35dbad1ff76e91c9abf62e629d4
Timestamp: 1718205594 Timestamp [UCT]: 2024-06-12 15:19:54 Age [y:d:h:m:s]: 01:149:14:19:37
Block: 1042684 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 365476 RingCT/type: yes/0
Extra: 015e89ce24620155c51df5e407dd665c7ae56fc35dbad1ff76e91c9abf62e629d40211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: abc5264c40069631fed94d5e02538245d9030aeed9d429ff35b9c6f887f02432 0.600000000000 1511659 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": 1042694, "vin": [ { "gen": { "height": 1042684 } } ], "vout": [ { "amount": 600000000, "target": { "key": "abc5264c40069631fed94d5e02538245d9030aeed9d429ff35b9c6f887f02432" } } ], "extra": [ 1, 94, 137, 206, 36, 98, 1, 85, 197, 29, 245, 228, 7, 221, 102, 92, 122, 229, 111, 195, 93, 186, 209, 255, 118, 233, 28, 154, 191, 98, 230, 41, 212, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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