Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fd402f810f675a17988fb3515f187ea5075cf99877e9a88a80786fa98bf0b4c4

Tx prefix hash: d10fc6673680762c0c4b885df0a1560b788a8fc845439fcfa5453256949e94ca
Tx public key: cc1667482b401bbdf8410c2b1954ed54a2336392e25753e86bc22d501c15d176
Timestamp: 1582196578 Timestamp [UCT]: 2020-02-20 11:02:58 Age [y:d:h:m:s]: 04:348:01:52:39
Block: 68801 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1140987 RingCT/type: yes/0
Extra: 01cc1667482b401bbdf8410c2b1954ed54a2336392e25753e86bc22d501c15d1760211000000018a2ee0d9000000000000000000

1 output(s) for total of 363.106925114000 dcy

stealth address amount amount idx
00: f4f2268aeeb4c237b883279eea7d673f3c2a5f05d52d98b221a07aa56c573cc1 363.106925114000 126824 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": 68811, "vin": [ { "gen": { "height": 68801 } } ], "vout": [ { "amount": 363106925114, "target": { "key": "f4f2268aeeb4c237b883279eea7d673f3c2a5f05d52d98b221a07aa56c573cc1" } } ], "extra": [ 1, 204, 22, 103, 72, 43, 64, 27, 189, 248, 65, 12, 43, 25, 84, 237, 84, 162, 51, 99, 146, 226, 87, 83, 232, 107, 194, 45, 80, 28, 21, 209, 118, 2, 17, 0, 0, 0, 1, 138, 46, 224, 217, 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