Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f917e3b69f77eb67c9c385a5b2e3913f25dabf2edda01b92c8f2d71d776e4dc8

Tx prefix hash: 9e7e4650a0fef8dcf8af8c444383fa106f3e7a3b6f88874293a5a8dbddb67b69
Tx public key: 6f63ac761e3c8ff57bcf2cf23f4a34a1bdf899a40c365dc6e610a36b14d1778d
Timestamp: 1714759491 Timestamp [UCT]: 2024-05-03 18:04:51 Age [y:d:h:m:s]: 00:204:13:16:14
Block: 1014119 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 146414 RingCT/type: yes/0
Extra: 016f63ac761e3c8ff57bcf2cf23f4a34a1bdf899a40c365dc6e610a36b14d1778d0211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 95f0a5577f73d68be65c9b9fbf99f23b871ce45c1c5d56c7bb5838e5d621ebe6 0.600000000000 1477116 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": 1014129, "vin": [ { "gen": { "height": 1014119 } } ], "vout": [ { "amount": 600000000, "target": { "key": "95f0a5577f73d68be65c9b9fbf99f23b871ce45c1c5d56c7bb5838e5d621ebe6" } } ], "extra": [ 1, 111, 99, 172, 118, 30, 60, 143, 245, 123, 207, 44, 242, 63, 74, 52, 161, 189, 248, 153, 164, 12, 54, 93, 198, 230, 16, 163, 107, 20, 209, 119, 141, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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