Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 933b5a148f5430296e69b15cdd3ebc23ef23f24573f49b709285b0ee5e218ee1

Tx prefix hash: 6d1bbb7de908a16c7b000790c1fad0fc5b0c1264fa6ddc15fc3a948734d084d3
Tx public key: 4ebb300ab30e2ed53f5a4ddc2f21b2a12e8ca6915481f6ec4a22be9cac27c351
Timestamp: 1728646289 Timestamp [UCT]: 2024-10-11 11:31:29 Age [y:d:h:m:s]: 00:165:09:20:55
Block: 1129240 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 117983 RingCT/type: yes/0
Extra: 014ebb300ab30e2ed53f5a4ddc2f21b2a12e8ca6915481f6ec4a22be9cac27c351021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9ca0273d8877b6797d9485c03859705381f9d58f87dde7df93aec084d2391f87 0.600000000000 1612065 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": 1129250, "vin": [ { "gen": { "height": 1129240 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9ca0273d8877b6797d9485c03859705381f9d58f87dde7df93aec084d2391f87" } } ], "extra": [ 1, 78, 187, 48, 10, 179, 14, 46, 213, 63, 90, 77, 220, 47, 33, 178, 161, 46, 140, 166, 145, 84, 129, 246, 236, 74, 34, 190, 156, 172, 39, 195, 81, 2, 17, 0, 0, 0, 5, 233, 20, 221, 21, 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