Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 364d572c7165afced74a204f2b30fbcf0387244e44f48b8a47a4d3b82423bb41

Tx prefix hash: 25cf8ad88c7180b97260bf42d3d3093dd4e4fbf1152ec48b1cab75501ba17b29
Tx public key: 49e5a5c54f3f55b5daa36937b39d5253c165a574501da4171c3aaa29b3031d38
Timestamp: 1608901955 Timestamp [UCT]: 2020-12-25 13:12:35 Age [y:d:h:m:s]: 03:340:00:00:17
Block: 169167 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 995129 RingCT/type: yes/0
Extra: 0149e5a5c54f3f55b5daa36937b39d5253c165a574501da4171c3aaa29b3031d38021100000008a45716b1000000000000000000

1 output(s) for total of 168.854736970000 dcy

stealth address amount amount idx
00: 4154a670502f1b5f891c5ad868239b5d8df5e3f0c013fc85514c0a1b30676148 168.854736970000 315222 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": 169177, "vin": [ { "gen": { "height": 169167 } } ], "vout": [ { "amount": 168854736970, "target": { "key": "4154a670502f1b5f891c5ad868239b5d8df5e3f0c013fc85514c0a1b30676148" } } ], "extra": [ 1, 73, 229, 165, 197, 79, 63, 85, 181, 218, 163, 105, 55, 179, 157, 82, 83, 193, 101, 165, 116, 80, 29, 164, 23, 28, 58, 170, 41, 179, 3, 29, 56, 2, 17, 0, 0, 0, 8, 164, 87, 22, 177, 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