Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 11f4e9e03c54c8f80e664adc21061cbb9bf288b53e84c69a77988e0e674fb3cb

Tx prefix hash: ee6f8873b8bee66f34da3466720f1878e5c806b8265a028dfca51bbe2165fc99
Tx public key: 004bf45818cadd32780c84dbd6581e1d5a2eb4310f1f34c1bcff7f4288212f52
Timestamp: 1718925423 Timestamp [UCT]: 2024-06-20 23:17:03 Age [y:d:h:m:s]: 00:291:23:47:57
Block: 1048644 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 208647 RingCT/type: yes/0
Extra: 01004bf45818cadd32780c84dbd6581e1d5a2eb4310f1f34c1bcff7f4288212f520211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cafba56cb14228be316ead534a203c69a66ae8ed1b78ccbe5bdd69c52f32b0d4 0.600000000000 1518729 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": 1048654, "vin": [ { "gen": { "height": 1048644 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cafba56cb14228be316ead534a203c69a66ae8ed1b78ccbe5bdd69c52f32b0d4" } } ], "extra": [ 1, 0, 75, 244, 88, 24, 202, 221, 50, 120, 12, 132, 219, 214, 88, 30, 29, 90, 46, 180, 49, 15, 31, 52, 193, 188, 255, 127, 66, 136, 33, 47, 82, 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