Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b9be0bc813d81145fa9286d7bdebe275dbb3a685b727d9aa5a1b7fa98fdde692

Tx prefix hash: 06e04c8322c6a4c1a7171b356045ba4c82e558a42484c5194f38d9b4fc1d910d
Tx public key: f9ccd7a7e69fc0f1adff109b167a322ea99d1cd626816fa46ac6a1d0f225830b
Timestamp: 1708281012 Timestamp [UCT]: 2024-02-18 18:30:12 Age [y:d:h:m:s]: 01:233:12:30:15
Block: 960400 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 425598 RingCT/type: yes/0
Extra: 01f9ccd7a7e69fc0f1adff109b167a322ea99d1cd626816fa46ac6a1d0f225830b02110000000a59dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2cb076bbcde4087d6dcfd74a7a7ac25811bcf20f8433c45e648820cd6ce301fd 0.600000000000 1419963 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": 960410, "vin": [ { "gen": { "height": 960400 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2cb076bbcde4087d6dcfd74a7a7ac25811bcf20f8433c45e648820cd6ce301fd" } } ], "extra": [ 1, 249, 204, 215, 167, 230, 159, 192, 241, 173, 255, 16, 155, 22, 122, 50, 46, 169, 157, 28, 214, 38, 129, 111, 164, 106, 198, 161, 208, 242, 37, 131, 11, 2, 17, 0, 0, 0, 10, 89, 218, 211, 245, 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