Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 91f0fbd6d48827a837a93be5c28e030ffaa0f26b8e45ba16d17703fab62c29c8

Tx prefix hash: 6b0b7b0df2870f8153894013031d96edb805cd73450af36b5a1eb1cf5a3bc8a7
Tx public key: 6ec476b8b96bad3e8c1e3ae72e4fda694f894d2397d9e211e7c9c4e833629042
Timestamp: 1704135243 Timestamp [UCT]: 2024-01-01 18:54:03 Age [y:d:h:m:s]: 01:129:12:07:42
Block: 926023 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 353689 RingCT/type: yes/0
Extra: 016ec476b8b96bad3e8c1e3ae72e4fda694f894d2397d9e211e7c9c4e8336290420211000000090011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 409cd658b6e4ad22df8bf7c11bd8ecf32f367ba835e9b9c8aeb503611296adc4 0.600000000000 1383793 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": 926033, "vin": [ { "gen": { "height": 926023 } } ], "vout": [ { "amount": 600000000, "target": { "key": "409cd658b6e4ad22df8bf7c11bd8ecf32f367ba835e9b9c8aeb503611296adc4" } } ], "extra": [ 1, 110, 196, 118, 184, 185, 107, 173, 62, 140, 30, 58, 231, 46, 79, 218, 105, 79, 137, 77, 35, 151, 217, 226, 17, 231, 201, 196, 232, 51, 98, 144, 66, 2, 17, 0, 0, 0, 9, 0, 17, 5, 91, 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