Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bc98b431e29eab1931b7e17702ec268f70ec930ac2ce2991ac082e14090d7967

Tx prefix hash: f17b5fc07dbcd4150682e70a11e2036b12c083f0a4b11a9bdedd06d1fb4496d3
Tx public key: 36270ac3676b3bcad8a4c7096e1f38d081750cc6b8c7b6e7527f201c3000f843
Timestamp: 1704036196 Timestamp [UCT]: 2023-12-31 15:23:16 Age [y:d:h:m:s]: 01:167:20:14:53
Block: 925200 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 381010 RingCT/type: yes/0
Extra: 0136270ac3676b3bcad8a4c7096e1f38d081750cc6b8c7b6e7527f201c3000f843021100000004e08532b6000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5989ffbb196df68dfd6ea3d957d6dff01f899e873b72dd134d172bfb5413b323 0.600000000000 1382960 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": 925210, "vin": [ { "gen": { "height": 925200 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5989ffbb196df68dfd6ea3d957d6dff01f899e873b72dd134d172bfb5413b323" } } ], "extra": [ 1, 54, 39, 10, 195, 103, 107, 59, 202, 216, 164, 199, 9, 110, 31, 56, 208, 129, 117, 12, 198, 184, 199, 182, 231, 82, 127, 32, 28, 48, 0, 248, 67, 2, 17, 0, 0, 0, 4, 224, 133, 50, 182, 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