Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1af1e166ed6020802b904b25665b734cc3ec83865d2f5a7cb5f691a977f32f06

Tx prefix hash: 0bd25800c97c14d747213113a9fb836ffb008b165ff20dc351e324f5c60cfbfa
Tx public key: f0a58fb7f3837e835a84c05b85439135a64cbcef72d90a4989a2a9c89c5599a6
Timestamp: 1731706306 Timestamp [UCT]: 2024-11-15 21:31:46 Age [y:d:h:m:s]: 00:142:07:01:32
Block: 1154505 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 101516 RingCT/type: yes/0
Extra: 01f0a58fb7f3837e835a84c05b85439135a64cbcef72d90a4989a2a9c89c5599a6021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8f54c60a3daafcd767e8aa3c53e1699912e363b1881117152cbaab5c2648a5b1 0.600000000000 1640118 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": 1154515, "vin": [ { "gen": { "height": 1154505 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8f54c60a3daafcd767e8aa3c53e1699912e363b1881117152cbaab5c2648a5b1" } } ], "extra": [ 1, 240, 165, 143, 183, 243, 131, 126, 131, 90, 132, 192, 91, 133, 67, 145, 53, 166, 76, 188, 239, 114, 217, 10, 73, 137, 162, 169, 200, 156, 85, 153, 166, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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