Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2afd57be56d7bd9378c5a081279eb6c925c5a9e110a7e9f1de51c9b9bf447d10

Tx prefix hash: 166b589902d9cc519e9deb3eb18be7227c4b428b242139ff167e99b1f9fe4c98
Tx public key: 8638a7605aff2bd621e371991c823acfe6d0d090e4a42b217c4697d5ecd45520
Timestamp: 1698750698 Timestamp [UCT]: 2023-10-31 11:11:38 Age [y:d:h:m:s]: 01:161:05:49:48
Block: 881606 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 376225 RingCT/type: yes/0
Extra: 018638a7605aff2bd621e371991c823acfe6d0d090e4a42b217c4697d5ecd4552002110000000475e3f0e9000000000000000000

1 output(s) for total of 0.735992452000 dcy

stealth address amount amount idx
00: 2e1adec385368b6d849fa79f64b549576b56e19711647f7da77092af06412b07 0.735992452000 1337204 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": 881616, "vin": [ { "gen": { "height": 881606 } } ], "vout": [ { "amount": 735992452, "target": { "key": "2e1adec385368b6d849fa79f64b549576b56e19711647f7da77092af06412b07" } } ], "extra": [ 1, 134, 56, 167, 96, 90, 255, 43, 214, 33, 227, 113, 153, 28, 130, 58, 207, 230, 208, 208, 144, 228, 164, 43, 33, 124, 70, 151, 213, 236, 212, 85, 32, 2, 17, 0, 0, 0, 4, 117, 227, 240, 233, 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