Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fb776815a6bf80b78299464fb628c8819f6a53522c59e809325e44c9e3a9fd40

Tx prefix hash: 34013174fe27e8b7a42aec89fdacd7229626d02f3da7aa0b89b1c1aca49e34c2
Tx public key: 0ee7ecfe4700d5d93a0c412026f1cd2250b8fb0efdb90322ba89254e35310649
Timestamp: 1733232960 Timestamp [UCT]: 2024-12-03 13:36:00 Age [y:d:h:m:s]: 00:118:04:44:35
Block: 1167159 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 84280 RingCT/type: yes/0
Extra: 010ee7ecfe4700d5d93a0c412026f1cd2250b8fb0efdb90322ba89254e3531064902110000000301491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 69722e72fb2c16619954220eaa4540f88c6afe6d1cc9e5424298a5818c513dc0 0.600000000000 1652854 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": 1167169, "vin": [ { "gen": { "height": 1167159 } } ], "vout": [ { "amount": 600000000, "target": { "key": "69722e72fb2c16619954220eaa4540f88c6afe6d1cc9e5424298a5818c513dc0" } } ], "extra": [ 1, 14, 231, 236, 254, 71, 0, 213, 217, 58, 12, 65, 32, 38, 241, 205, 34, 80, 184, 251, 14, 253, 185, 3, 34, 186, 137, 37, 78, 53, 49, 6, 73, 2, 17, 0, 0, 0, 3, 1, 73, 31, 136, 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