Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 89d1e33dea08b68f9c5918da22fba00277673cfb97d18c76611059b4a9df4db6

Tx prefix hash: 1c27c7792c7ff19ff9830dc80f610e1f2a4c4a033078bf38242a118c2f73ed6e
Tx public key: 400ac03b5120a17384aa9bf1e808caff9bf9164f042cd009e920d183fdbea445
Timestamp: 1714703080 Timestamp [UCT]: 2024-05-03 02:24:40 Age [y:d:h:m:s]: 01:189:19:00:52
Block: 1013653 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 394260 RingCT/type: yes/0
Extra: 01400ac03b5120a17384aa9bf1e808caff9bf9164f042cd009e920d183fdbea4450211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 868d0deeefe6bd42bdf633bff51bb5f87603d9bdc4e7c73cce46dacf923e0dac 0.600000000000 1476524 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": 1013663, "vin": [ { "gen": { "height": 1013653 } } ], "vout": [ { "amount": 600000000, "target": { "key": "868d0deeefe6bd42bdf633bff51bb5f87603d9bdc4e7c73cce46dacf923e0dac" } } ], "extra": [ 1, 64, 10, 192, 59, 81, 32, 161, 115, 132, 170, 155, 241, 232, 8, 202, 255, 155, 249, 22, 79, 4, 44, 208, 9, 233, 32, 209, 131, 253, 190, 164, 69, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 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