Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b5ede9f8b55f260ca82ef06ee34f55663415ceb75a35e2fcd0a82f90af181aa4

Tx prefix hash: aa2035e8a09281326aa1d5f723103c9f8ecd1b1244b91934b117eefcace55ba0
Tx public key: 3ac94aec0f12ed167ca34bddfe7dcb7b43a585fc23334c6726645b2d3d6e2ccc
Timestamp: 1711979748 Timestamp [UCT]: 2024-04-01 13:55:48 Age [y:d:h:m:s]: 01:076:07:09:53
Block: 991034 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 315461 RingCT/type: yes/0
Extra: 013ac94aec0f12ed167ca34bddfe7dcb7b43a585fc23334c6726645b2d3d6e2ccc02110000000659dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 58d1ee95a455514609f8a25a102558c98677381212fb239e04a2a854f56902f4 0.600000000000 1451366 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": 991044, "vin": [ { "gen": { "height": 991034 } } ], "vout": [ { "amount": 600000000, "target": { "key": "58d1ee95a455514609f8a25a102558c98677381212fb239e04a2a854f56902f4" } } ], "extra": [ 1, 58, 201, 74, 236, 15, 18, 237, 22, 124, 163, 75, 221, 254, 125, 203, 123, 67, 165, 133, 252, 35, 51, 76, 103, 38, 100, 91, 45, 61, 110, 44, 204, 2, 17, 0, 0, 0, 6, 89, 218, 211, 245, 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