Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 031a8652f25b1bce8fd5dde24cf485293b46640d1d371dbb190fa829ec8a44ef

Tx prefix hash: 2b2e1a1db4c6d7a471d59dc059cbe4fc94dee6956761f1d3107823960ce855c9
Tx public key: a57141b26daf8a5c4b4321121cc4cedf544ccb13fa0a2db8145065cacc0cd116
Timestamp: 1697379324 Timestamp [UCT]: 2023-10-15 14:15:24 Age [y:d:h:m:s]: 01:185:20:16:28
Block: 870222 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 393863 RingCT/type: yes/0
Extra: 01a57141b26daf8a5c4b4321121cc4cedf544ccb13fa0a2db8145065cacc0cd11602110000000133af99f4000000000000000000

1 output(s) for total of 0.802813993000 dcy

stealth address amount amount idx
00: 002e7e4c82dc916dec230c9f0c75af4b12af9d3b8b0fb47385aa583e15f96361 0.802813993000 1325095 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": 870232, "vin": [ { "gen": { "height": 870222 } } ], "vout": [ { "amount": 802813993, "target": { "key": "002e7e4c82dc916dec230c9f0c75af4b12af9d3b8b0fb47385aa583e15f96361" } } ], "extra": [ 1, 165, 113, 65, 178, 109, 175, 138, 92, 75, 67, 33, 18, 28, 196, 206, 223, 84, 76, 203, 19, 250, 10, 45, 184, 20, 80, 101, 202, 204, 12, 209, 22, 2, 17, 0, 0, 0, 1, 51, 175, 153, 244, 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