Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 62fc278c62a2a54ac1e6f819e8618f17ad320cbe900b580776f2531fc74ad418

Tx prefix hash: 3f0b835a62081e8e493c5a0355da4c21f283fa71a04b0603529084937eadd92f
Tx public key: 8e06327e5889500b81a494196a12ebe0265ba3e8bf8272d5f2d19aeffc803e04
Timestamp: 1739452983 Timestamp [UCT]: 2025-02-13 13:23:03 Age [y:d:h:m:s]: 00:278:09:48:31
Block: 1218398 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 196726 RingCT/type: yes/0
Extra: 018e06327e5889500b81a494196a12ebe0265ba3e8bf8272d5f2d19aeffc803e04021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4385f6885ba26ae5e5edc3b36f03383c8b6efe8aaedb0f3b062b7a4a840beee7 0.600000000000 1705213 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": 1218408, "vin": [ { "gen": { "height": 1218398 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4385f6885ba26ae5e5edc3b36f03383c8b6efe8aaedb0f3b062b7a4a840beee7" } } ], "extra": [ 1, 142, 6, 50, 126, 88, 137, 80, 11, 129, 164, 148, 25, 106, 18, 235, 224, 38, 91, 163, 232, 191, 130, 114, 213, 242, 209, 154, 239, 252, 128, 62, 4, 2, 17, 0, 0, 0, 5, 0, 127, 151, 138, 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