Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 88f1ff1fb345187c21ab0647463475f56734594da16b94d27df9125d43b0bd89

Tx prefix hash: 3ec7d329bc96bf3fcb9e5090c86ac2dee911c711623fcd944f3e6d22196a28a9
Tx public key: f9c597c9ee51b39606ef507fe9480bd7fb64a3cc8c46ea6ca66ef649e2b8d05b
Timestamp: 1578858005 Timestamp [UCT]: 2020-01-12 19:40:05 Age [y:d:h:m:s]: 05:142:05:09:50
Block: 44165 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1251835 RingCT/type: yes/0
Extra: 01f9c597c9ee51b39606ef507fe9480bd7fb64a3cc8c46ea6ca66ef649e2b8d05b0211000000114943cd9f000000000000000000

1 output(s) for total of 438.191413094000 dcy

stealth address amount amount idx
00: ca289150d27c0a2ede157148b2ceaf0b472d3b8c4a4a24b4da50a2a1134fc459 438.191413094000 80280 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": 44175, "vin": [ { "gen": { "height": 44165 } } ], "vout": [ { "amount": 438191413094, "target": { "key": "ca289150d27c0a2ede157148b2ceaf0b472d3b8c4a4a24b4da50a2a1134fc459" } } ], "extra": [ 1, 249, 197, 151, 201, 238, 81, 179, 150, 6, 239, 80, 127, 233, 72, 11, 215, 251, 100, 163, 204, 140, 70, 234, 108, 166, 110, 246, 73, 226, 184, 208, 91, 2, 17, 0, 0, 0, 17, 73, 67, 205, 159, 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