Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 84e9203a25cb2fc44bcb98f929a1a8646f21c5abc56841cece60f2e692b7722f

Tx prefix hash: 66c1a44d75744dd908e2435f6d0b7bf0df070ee53384ae89da6d51880ebddaef
Tx public key: fb6ef45612e97a7b3ae567e6a1ff2e5e44417f0cbd84c69e53e27042730880ca
Timestamp: 1725597555 Timestamp [UCT]: 2024-09-06 04:39:15 Age [y:d:h:m:s]: 01:063:20:14:23
Block: 1103966 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 304048 RingCT/type: yes/0
Extra: 01fb6ef45612e97a7b3ae567e6a1ff2e5e44417f0cbd84c69e53e27042730880ca02110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 65281f928530d0eec62dc3938708237cbfd3f05d572c997f932295a4ece5dcd7 0.600000000000 1580997 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": 1103976, "vin": [ { "gen": { "height": 1103966 } } ], "vout": [ { "amount": 600000000, "target": { "key": "65281f928530d0eec62dc3938708237cbfd3f05d572c997f932295a4ece5dcd7" } } ], "extra": [ 1, 251, 110, 244, 86, 18, 233, 122, 123, 58, 229, 103, 230, 161, 255, 46, 94, 68, 65, 127, 12, 189, 132, 198, 158, 83, 226, 112, 66, 115, 8, 128, 202, 2, 17, 0, 0, 0, 4, 145, 225, 60, 4, 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