Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: db01355163dd1934baf323f9268527ec8621f0fa664784be305d07b6182559a4

Tx prefix hash: b2e2b7d2f1b6505d24dc7c42cb134d87e52bfec2701e473140ca0ffd4b2f7f1b
Tx public key: bcd5a466c9ec07d28a5e0a5a94d1fa864883ba140e0c1954b63c74fe3526b557
Timestamp: 1677524399 Timestamp [UCT]: 2023-02-27 18:59:59 Age [y:d:h:m:s]: 02:042:20:03:06
Block: 706298 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 552195 RingCT/type: yes/0
Extra: 01bcd5a466c9ec07d28a5e0a5a94d1fa864883ba140e0c1954b63c74fe3526b55702110000000683600029000000000000000000

1 output(s) for total of 2.803763849000 dcy

stealth address amount amount idx
00: 1aeaa3bd135f61ff84d4a614db658d372a03b9c4d5d0954200b51def3539e3e8 2.803763849000 1150027 of 0

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": 706308, "vin": [ { "gen": { "height": 706298 } } ], "vout": [ { "amount": 2803763849, "target": { "key": "1aeaa3bd135f61ff84d4a614db658d372a03b9c4d5d0954200b51def3539e3e8" } } ], "extra": [ 1, 188, 213, 164, 102, 201, 236, 7, 210, 138, 94, 10, 90, 148, 209, 250, 134, 72, 131, 186, 20, 14, 12, 25, 84, 182, 60, 116, 254, 53, 38, 181, 87, 2, 17, 0, 0, 0, 6, 131, 96, 0, 41, 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