Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 86582367ffcb6419a377b8fe997d950203c5a0a4a513a9b0210da0400366b7d2

Tx prefix hash: 1fe9abbe524576450d3fe453bb0468508a34ed7ff93adc3d33f509e37c90edd9
Tx public key: 49a00936b85d5c77baa760182c7b44c953cd3dd1d916aac9b3ae905ea3c4a28d
Timestamp: 1731408123 Timestamp [UCT]: 2024-11-12 10:42:03 Age [y:d:h:m:s]: 00:142:15:00:56
Block: 1152043 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 101751 RingCT/type: yes/0
Extra: 0149a00936b85d5c77baa760182c7b44c953cd3dd1d916aac9b3ae905ea3c4a28d021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 358debedc1585f25a9b628ad65f8476f7b884ff655330d93460dafa9020692f1 0.600000000000 1637634 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": 1152053, "vin": [ { "gen": { "height": 1152043 } } ], "vout": [ { "amount": 600000000, "target": { "key": "358debedc1585f25a9b628ad65f8476f7b884ff655330d93460dafa9020692f1" } } ], "extra": [ 1, 73, 160, 9, 54, 184, 93, 92, 119, 186, 167, 96, 24, 44, 123, 68, 201, 83, 205, 61, 209, 217, 22, 170, 201, 179, 174, 144, 94, 163, 196, 162, 141, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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