Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 66f029a0d872e0c3e0263e4c1bf22a2163b9600e1aac1c36d1a43ddbfc282437

Tx prefix hash: 5fae81a054a653961a9f77a9385dab0105643e5db8a4f690efe40212f15982c2
Tx public key: ec43e71dd52cc2a26a0e5e42a82313e65d4a09ed37bef4f9c97a0f66a50f397e
Timestamp: 1581976354 Timestamp [UCT]: 2020-02-17 21:52:34 Age [y:d:h:m:s]: 04:318:00:51:33
Block: 67048 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1119695 RingCT/type: yes/0
Extra: 01ec43e71dd52cc2a26a0e5e42a82313e65d4a09ed37bef4f9c97a0f66a50f397e02110000002a4943cd9f000000000000000000

1 output(s) for total of 367.995875441000 dcy

stealth address amount amount idx
00: a615c78f6bfa5919150fe7a910c95ee925fa57e5bd652319b754cfb9f442b44e 367.995875441000 123498 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": 67058, "vin": [ { "gen": { "height": 67048 } } ], "vout": [ { "amount": 367995875441, "target": { "key": "a615c78f6bfa5919150fe7a910c95ee925fa57e5bd652319b754cfb9f442b44e" } } ], "extra": [ 1, 236, 67, 231, 29, 213, 44, 194, 162, 106, 14, 94, 66, 168, 35, 19, 230, 93, 74, 9, 237, 55, 190, 244, 249, 201, 122, 15, 102, 165, 15, 57, 126, 2, 17, 0, 0, 0, 42, 73, 67, 205, 159, 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