Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8d9dde6c5e48a7de9ad154e2cf3798a90cf28b29155ffe9cca226cad8193a791

Tx prefix hash: b48272df726a81f34abaaf66d79596d1cef3e17062fdb6b6472fc7b5ceac3d64
Tx public key: d5be83350cc9b4ef8674a56484773dac7f2d4f27196f70b725ce5fc3ca7df8cf
Timestamp: 1705630494 Timestamp [UCT]: 2024-01-19 02:14:54 Age [y:d:h:m:s]: 01:306:22:05:01
Block: 938400 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 478176 RingCT/type: yes/0
Extra: 01d5be83350cc9b4ef8674a56484773dac7f2d4f27196f70b725ce5fc3ca7df8cf0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 60f8f41d33bb86c921476647a1bf71b68d09e265409149eb84c6a53f112bb1f9 0.600000000000 1396470 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": 938410, "vin": [ { "gen": { "height": 938400 } } ], "vout": [ { "amount": 600000000, "target": { "key": "60f8f41d33bb86c921476647a1bf71b68d09e265409149eb84c6a53f112bb1f9" } } ], "extra": [ 1, 213, 190, 131, 53, 12, 201, 180, 239, 134, 116, 165, 100, 132, 119, 61, 172, 127, 45, 79, 39, 25, 111, 112, 183, 37, 206, 95, 195, 202, 125, 248, 207, 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