Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 588436e9c792565f8637f17775b88fd83534cf5a0ce47224e94d4da3a954314f

Tx prefix hash: 68ef6dd07a6475e553a8cf5702a5ea093e487ca795c7dcab4b7ca08efbc4558c
Tx public key: cae7eed7ae372aaf926fea2f0124fd54370dc52f197ef5faff5aecab4e17059a
Timestamp: 1721595010 Timestamp [UCT]: 2024-07-21 20:50:10 Age [y:d:h:m:s]: 01:120:20:23:21
Block: 1070764 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 344904 RingCT/type: yes/0
Extra: 01cae7eed7ae372aaf926fea2f0124fd54370dc52f197ef5faff5aecab4e17059a02110000000691e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3054058cf0a14e0d30c46ec176c55d7e58464b7a4b3295aea1de8f62b396ed38 0.600000000000 1542733 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": 1070774, "vin": [ { "gen": { "height": 1070764 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3054058cf0a14e0d30c46ec176c55d7e58464b7a4b3295aea1de8f62b396ed38" } } ], "extra": [ 1, 202, 231, 238, 215, 174, 55, 42, 175, 146, 111, 234, 47, 1, 36, 253, 84, 55, 13, 197, 47, 25, 126, 245, 250, 255, 90, 236, 171, 78, 23, 5, 154, 2, 17, 0, 0, 0, 6, 145, 225, 60, 4, 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