Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1e8947c453b8ad51cc405885fc85f54f739fd235c826a5a428a05a9f8417098d

Tx prefix hash: d6ec996fa182a435b4b4ea6cedd73d9ad6be08aefac280e262b6dc000032e8b1
Tx public key: b9db12e83bbfc7d63075fec1da1710c9a37522f1d9d98a5d836eb31000f169a0
Timestamp: 1720308614 Timestamp [UCT]: 2024-07-06 23:30:14 Age [y:d:h:m:s]: 00:269:14:42:35
Block: 1060103 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 192649 RingCT/type: yes/0
Extra: 01b9db12e83bbfc7d63075fec1da1710c9a37522f1d9d98a5d836eb31000f169a0021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 56d4e92cf3746b6f21ce25e5d03a3d4a177668a1e4404af07e236a19d24abf10 0.600000000000 1530574 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": 1060113, "vin": [ { "gen": { "height": 1060103 } } ], "vout": [ { "amount": 600000000, "target": { "key": "56d4e92cf3746b6f21ce25e5d03a3d4a177668a1e4404af07e236a19d24abf10" } } ], "extra": [ 1, 185, 219, 18, 232, 59, 191, 199, 214, 48, 117, 254, 193, 218, 23, 16, 201, 163, 117, 34, 241, 217, 217, 138, 93, 131, 110, 179, 16, 0, 241, 105, 160, 2, 17, 0, 0, 0, 6, 233, 20, 221, 21, 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