Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 193b185780e6fb75dd9853a80d6f14ef789b8a8a63b7c931b9e6871b25a37a2a

Tx prefix hash: e65a0d2d82c5f79e5e007464162c60098d67e1e366a6d9926a8b2dec2855d1e4
Tx public key: 79b48307eb8b6c9a68dad13ce1d4868a56c3b8359be968740ed303dab8ba0640
Timestamp: 1715063324 Timestamp [UCT]: 2024-05-07 06:28:44 Age [y:d:h:m:s]: 00:333:12:04:59
Block: 1016635 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 238382 RingCT/type: yes/0
Extra: 0179b48307eb8b6c9a68dad13ce1d4868a56c3b8359be968740ed303dab8ba06400211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: eb8c0f5927b13671d0ece03b67e13a59028033185a878d88e07a9180f0afc92d 0.600000000000 1480276 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": 1016645, "vin": [ { "gen": { "height": 1016635 } } ], "vout": [ { "amount": 600000000, "target": { "key": "eb8c0f5927b13671d0ece03b67e13a59028033185a878d88e07a9180f0afc92d" } } ], "extra": [ 1, 121, 180, 131, 7, 235, 139, 108, 154, 104, 218, 209, 60, 225, 212, 134, 138, 86, 195, 184, 53, 155, 233, 104, 116, 14, 211, 3, 218, 184, 186, 6, 64, 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