Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8578eca796c9dfee54085c66eb7b5cd4ac4c2409b0c804d02c97a0d38f69de3d

Tx prefix hash: a9b23c49a2c9e208424396c7f51acba630f63a062af77e35f23d611c38a73f3b
Tx public key: 220bfc35063696c905a3f3528947ee386cd60081e36695ae7f063f1fa636c45d
Timestamp: 1700762109 Timestamp [UCT]: 2023-11-23 17:55:09 Age [y:d:h:m:s]: 01:177:07:41:34
Block: 898064 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 387921 RingCT/type: yes/0
Extra: 01220bfc35063696c905a3f3528947ee386cd60081e36695ae7f063f1fa636c45d02110000000175e3f0e9000000000000000000

1 output(s) for total of 0.649144154000 dcy

stealth address amount amount idx
00: ebb7a5758037660cea1c527dad202a75ec6387e3ead6f9e7a9ac9f5396ce0f20 0.649144154000 1354467 of 0

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": 898074, "vin": [ { "gen": { "height": 898064 } } ], "vout": [ { "amount": 649144154, "target": { "key": "ebb7a5758037660cea1c527dad202a75ec6387e3ead6f9e7a9ac9f5396ce0f20" } } ], "extra": [ 1, 34, 11, 252, 53, 6, 54, 150, 201, 5, 163, 243, 82, 137, 71, 238, 56, 108, 214, 0, 129, 227, 102, 149, 174, 127, 6, 63, 31, 166, 54, 196, 93, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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