Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 276f7c5b90eab53da610107eebd41569cc48f34f1b42cc4f7ae1af4ebbd6ec79

Tx prefix hash: 108a5931ebe7e1add3e2ec0ba19ec7fef589b82b8acda2b516751a624ae1c88d
Tx public key: 2adf0bbe8bcff55f2d914765642736bd164a1e7900b70c47a070b280ee44c6d9
Timestamp: 1714977490 Timestamp [UCT]: 2024-05-06 06:38:10 Age [y:d:h:m:s]: 00:202:20:52:37
Block: 1015921 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 145214 RingCT/type: yes/0
Extra: 012adf0bbe8bcff55f2d914765642736bd164a1e7900b70c47a070b280ee44c6d90211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dbac6c87ac5774f1ae83ea005978b0bd494a87aed4edc7acb5f9b468c620d3e4 0.600000000000 1479364 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": 1015931, "vin": [ { "gen": { "height": 1015921 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dbac6c87ac5774f1ae83ea005978b0bd494a87aed4edc7acb5f9b468c620d3e4" } } ], "extra": [ 1, 42, 223, 11, 190, 139, 207, 245, 95, 45, 145, 71, 101, 100, 39, 54, 189, 22, 74, 30, 121, 0, 183, 12, 71, 160, 112, 178, 128, 238, 68, 198, 217, 2, 17, 0, 0, 0, 2, 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