Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 48c791418367d8e86a0652eb6d7b6a0ee9bf751e50a9a5546bdba7f2b6a91291

Tx prefix hash: f168e833fd7b3b9824decd5ca647808bd0fa2564d5f7a549cd9c6159c4684b5d
Tx public key: ec4a22ede2fc1d0b939875795332c95908cfbea9616b5d552249c0691c89bf84
Timestamp: 1700472622 Timestamp [UCT]: 2023-11-20 09:30:22 Age [y:d:h:m:s]: 01:132:08:45:50
Block: 895670 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 355766 RingCT/type: yes/0
Extra: 01ec4a22ede2fc1d0b939875795332c95908cfbea9616b5d552249c0691c89bf8402110000000275e3f0e9000000000000000000

1 output(s) for total of 0.661109609000 dcy

stealth address amount amount idx
00: 8606639db2b43f06910e1f0d5363462a0187747d6bc71bf47b995a7e31a204c6 0.661109609000 1351911 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": 895680, "vin": [ { "gen": { "height": 895670 } } ], "vout": [ { "amount": 661109609, "target": { "key": "8606639db2b43f06910e1f0d5363462a0187747d6bc71bf47b995a7e31a204c6" } } ], "extra": [ 1, 236, 74, 34, 237, 226, 252, 29, 11, 147, 152, 117, 121, 83, 50, 201, 89, 8, 207, 190, 169, 97, 107, 93, 85, 34, 73, 192, 105, 28, 137, 191, 132, 2, 17, 0, 0, 0, 2, 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