Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ffd9575a79f5212c48ac7f9f4658fa66abc4be7ffef170683f628f5a7dc6f649

Tx prefix hash: 0ba6776e3cbc77faff3c535657d8c97612bade8d8acdea3e1b8007f24c44e6eb
Tx public key: cd66f1de15af68f7d54f55a3ef00f143872c8258ca27affca4e34324c37b096b
Timestamp: 1694726482 Timestamp [UCT]: 2023-09-14 21:21:22 Age [y:d:h:m:s]: 01:204:00:17:14
Block: 848204 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 406907 RingCT/type: yes/0
Extra: 01cd66f1de15af68f7d54f55a3ef00f143872c8258ca27affca4e34324c37b096b02110000000433af99f4000000000000000000

1 output(s) for total of 0.949616170000 dcy

stealth address amount amount idx
00: 19025abb33c41116810ca8e6065df7490137061c487322352c74f8e81b455aa6 0.949616170000 1301792 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": 848214, "vin": [ { "gen": { "height": 848204 } } ], "vout": [ { "amount": 949616170, "target": { "key": "19025abb33c41116810ca8e6065df7490137061c487322352c74f8e81b455aa6" } } ], "extra": [ 1, 205, 102, 241, 222, 21, 175, 104, 247, 213, 79, 85, 163, 239, 0, 241, 67, 135, 44, 130, 88, 202, 39, 175, 252, 164, 227, 67, 36, 195, 123, 9, 107, 2, 17, 0, 0, 0, 4, 51, 175, 153, 244, 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