Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8cec67fd76f1766c792e6d673f4d4126bdce2f93cdc5515d6fef0bc4670bc8a2

Tx prefix hash: 15c3d91a764007d60f8a95aefbd53e8f028e1a7499dbbbf3e496071ab418e6bf
Tx public key: 67165186d6b18ecfc0870314f5db2e7d7fd3b788aebc182920946b0fabc71e20
Timestamp: 1701162422 Timestamp [UCT]: 2023-11-28 09:07:02 Age [y:d:h:m:s]: 01:129:14:09:15
Block: 901379 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 353779 RingCT/type: yes/0
Extra: 0167165186d6b18ecfc0870314f5db2e7d7fd3b788aebc182920946b0fabc71e2002110000001275e3f0e9000000000000000000

1 output(s) for total of 0.632932176000 dcy

stealth address amount amount idx
00: b9fd8b8fb05f8975a92c92751db74475a32848b03e4a3eacc3c82486aa085e0e 0.632932176000 1357938 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": 901389, "vin": [ { "gen": { "height": 901379 } } ], "vout": [ { "amount": 632932176, "target": { "key": "b9fd8b8fb05f8975a92c92751db74475a32848b03e4a3eacc3c82486aa085e0e" } } ], "extra": [ 1, 103, 22, 81, 134, 214, 177, 142, 207, 192, 135, 3, 20, 245, 219, 46, 125, 127, 211, 183, 136, 174, 188, 24, 41, 32, 148, 107, 15, 171, 199, 30, 32, 2, 17, 0, 0, 0, 18, 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