Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b9884772da8e3bf0c9694756ec937f36d24b24a1f93248e9aefc20d28e1d0d79

Tx prefix hash: 4580dc171ae5919cb0d4f6d647c24cddaed47db379468efb33ca760575a29ae0
Tx public key: f5ea9fd94593b69bd6697b3482d43cbca142efc20c3417a8b46d605d69ef52fd
Timestamp: 1715059096 Timestamp [UCT]: 2024-05-07 05:18:16 Age [y:d:h:m:s]: 01:209:17:57:12
Block: 1016597 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 408559 RingCT/type: yes/0
Extra: 01f5ea9fd94593b69bd6697b3482d43cbca142efc20c3417a8b46d605d69ef52fd0211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 837c479c1478e196d96d4152b24a0c262fa80513ad0646d6e90e549b87434a5b 0.600000000000 1480226 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": 1016607, "vin": [ { "gen": { "height": 1016597 } } ], "vout": [ { "amount": 600000000, "target": { "key": "837c479c1478e196d96d4152b24a0c262fa80513ad0646d6e90e549b87434a5b" } } ], "extra": [ 1, 245, 234, 159, 217, 69, 147, 182, 155, 214, 105, 123, 52, 130, 212, 60, 188, 161, 66, 239, 194, 12, 52, 23, 168, 180, 109, 96, 93, 105, 239, 82, 253, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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