Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: abb3540db451bf0db9e28af2f6344b75f2750c02c5316cbd763b16d511bd2612

Tx prefix hash: 6d67f281bd361731fa0e0f9f3436f6bbdda8f711f763fc871dd1bc102b3a3699
Tx public key: 716992f0cced912cd9ca7f56b947f7229452d1e625e9f72b7ff24e092bbf2644
Timestamp: 1706384139 Timestamp [UCT]: 2024-01-27 19:35:39 Age [y:d:h:m:s]: 01:291:11:06:58
Block: 944646 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 467132 RingCT/type: yes/0
Extra: 01716992f0cced912cd9ca7f56b947f7229452d1e625e9f72b7ff24e092bbf264402110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 64fab7a185035bcca0728712fe5eecb495b6a662773bb44f49c6ca6c666638ab 0.600000000000 1402932 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": 944656, "vin": [ { "gen": { "height": 944646 } } ], "vout": [ { "amount": 600000000, "target": { "key": "64fab7a185035bcca0728712fe5eecb495b6a662773bb44f49c6ca6c666638ab" } } ], "extra": [ 1, 113, 105, 146, 240, 204, 237, 145, 44, 217, 202, 127, 86, 185, 71, 247, 34, 148, 82, 209, 230, 37, 233, 247, 43, 127, 242, 78, 9, 43, 191, 38, 68, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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