Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b5d94f280c75237e9c6a1956f3766bdf92bb1fe058eceacd4528177979096303

Tx prefix hash: 32e30f8eb802aeb6e119819574b9be9b364c6b6a168d86710e3778be6d5b875a
Tx public key: 296c8aeef67fa818c79b8c1b3fd34137daaa0cc9af4c8599876d963613ec81f3
Timestamp: 1703119998 Timestamp [UCT]: 2023-12-21 00:53:18 Age [y:d:h:m:s]: 01:128:07:50:35
Block: 917633 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 352833 RingCT/type: yes/0
Extra: 01296c8aeef67fa818c79b8c1b3fd34137daaa0cc9af4c8599876d963613ec81f3021100000002c5452960000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5cab595cb1205a181363575251c19ed0817f235fd9f967a0ee7d45f3ddd48edc 0.600000000000 1375215 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": 917643, "vin": [ { "gen": { "height": 917633 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5cab595cb1205a181363575251c19ed0817f235fd9f967a0ee7d45f3ddd48edc" } } ], "extra": [ 1, 41, 108, 138, 238, 246, 127, 168, 24, 199, 155, 140, 27, 63, 211, 65, 55, 218, 170, 12, 201, 175, 76, 133, 153, 135, 109, 150, 54, 19, 236, 129, 243, 2, 17, 0, 0, 0, 2, 197, 69, 41, 96, 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