Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: deb7cd6b240bdf5c838987eb1ebe0892929fa95128066fe8cce21527f2906381

Tx prefix hash: d2457a9b874d82be44e92e78cfc2a6df1003f3cb19e1073d325557f4aabece09
Tx public key: e2e21d65f1c5348863a9cb7afcaae761b06ef90ffa4a9967dcff49d5072499f9
Timestamp: 1710569379 Timestamp [UCT]: 2024-03-16 06:09:39 Age [y:d:h:m:s]: 01:009:10:27:59
Block: 979394 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 267694 RingCT/type: yes/0
Extra: 01e2e21d65f1c5348863a9cb7afcaae761b06ef90ffa4a9967dcff49d5072499f902110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fd06f3e53f61a10fb6126fbd5920b8773ddc9ecdb46f937ed3c90b1c2567f273 0.600000000000 1439427 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": 979404, "vin": [ { "gen": { "height": 979394 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fd06f3e53f61a10fb6126fbd5920b8773ddc9ecdb46f937ed3c90b1c2567f273" } } ], "extra": [ 1, 226, 226, 29, 101, 241, 197, 52, 136, 99, 169, 203, 122, 252, 170, 231, 97, 176, 110, 249, 15, 250, 74, 153, 103, 220, 255, 73, 213, 7, 36, 153, 249, 2, 17, 0, 0, 0, 5, 89, 218, 211, 245, 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