Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a46d6a6adb3f9185333320f7053ee503be749a39c1fef49214c893588a82a835

Tx prefix hash: 100478023adaf37e77322210dc155ec4f9f535b37bda0deceb96564b02ea55b3
Tx public key: 66f8186a5d1f7f8a9f867b8a1283c2a745cbf13dfabe9ba32f81b110fbda492b
Timestamp: 1710550043 Timestamp [UCT]: 2024-03-16 00:47:23 Age [y:d:h:m:s]: 01:042:12:13:02
Block: 979227 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 291374 RingCT/type: yes/0
Extra: 0166f8186a5d1f7f8a9f867b8a1283c2a745cbf13dfabe9ba32f81b110fbda492b0211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a641a1c2add9eb12386d5c8db913f37056ba92f72289adc4ce67cc636b1d93c1 0.600000000000 1439260 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": 979237, "vin": [ { "gen": { "height": 979227 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a641a1c2add9eb12386d5c8db913f37056ba92f72289adc4ce67cc636b1d93c1" } } ], "extra": [ 1, 102, 248, 24, 106, 93, 31, 127, 138, 159, 134, 123, 138, 18, 131, 194, 167, 69, 203, 241, 61, 250, 190, 155, 163, 47, 129, 177, 16, 251, 218, 73, 43, 2, 17, 0, 0, 0, 3, 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