Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 07f28aabe5f919cce7b320c923c121a0fcc4a35a456f6e442eb097d76e64ba32

Tx prefix hash: 958cec2057b7af3a1589f5af91d3608314a1b7c4c330836b1a19fc59d6d95ff7
Tx public key: 83c15b0232632b243abac8ed9108f3e0971ce535c56a04aa3ae9179a1ee12579
Timestamp: 1686114750 Timestamp [UCT]: 2023-06-07 05:12:30 Age [y:d:h:m:s]: 01:320:18:46:37
Block: 776874 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 490456 RingCT/type: yes/0
Extra: 0183c15b0232632b243abac8ed9108f3e0971ce535c56a04aa3ae9179a1ee12579021100000002faf35c9c000000000000000000

1 output(s) for total of 1.636417465000 dcy

stealth address amount amount idx
00: d2a3a6feff6df0bc9f6e3666cb5f387e4adcf712fc1f2e0dc6cd37c849596f1b 1.636417465000 1226441 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": 776884, "vin": [ { "gen": { "height": 776874 } } ], "vout": [ { "amount": 1636417465, "target": { "key": "d2a3a6feff6df0bc9f6e3666cb5f387e4adcf712fc1f2e0dc6cd37c849596f1b" } } ], "extra": [ 1, 131, 193, 91, 2, 50, 99, 43, 36, 58, 186, 200, 237, 145, 8, 243, 224, 151, 28, 229, 53, 197, 106, 4, 170, 58, 233, 23, 154, 30, 225, 37, 121, 2, 17, 0, 0, 0, 2, 250, 243, 92, 156, 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