Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 033b348cc8e0c53b869906eaab186a3e7e44aff53d9e835d1dca1f69ab627a87

Tx prefix hash: 229bfe5cde2f498850418ff768cbffb0704be85b8e2781e915d61aee7f5e022b
Tx public key: c4ccdc6ca0aad0846c9f1f9632aaa4cd9cc8cd54461b9246ff0a7f29c09b214a
Timestamp: 1632154669 Timestamp [UCT]: 2021-09-20 16:17:49 Age [y:d:h:m:s]: 03:117:00:23:43
Block: 337635 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 859666 RingCT/type: yes/0
Extra: 01c4ccdc6ca0aad0846c9f1f9632aaa4cd9cc8cd54461b9246ff0a7f29c09b214a0211000000605d7cc334000000000000000000

1 output(s) for total of 46.695552858000 dcy

stealth address amount amount idx
00: b6173e4e07f4fe4cd6dd69db25b6e583b6b1d2f74ee950212de6b738cb5df59a 46.695552858000 695166 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": 337645, "vin": [ { "gen": { "height": 337635 } } ], "vout": [ { "amount": 46695552858, "target": { "key": "b6173e4e07f4fe4cd6dd69db25b6e583b6b1d2f74ee950212de6b738cb5df59a" } } ], "extra": [ 1, 196, 204, 220, 108, 160, 170, 208, 132, 108, 159, 31, 150, 50, 170, 164, 205, 156, 200, 205, 84, 70, 27, 146, 70, 255, 10, 127, 41, 192, 155, 33, 74, 2, 17, 0, 0, 0, 96, 93, 124, 195, 52, 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