Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7519125bf2e105b0f92da40b693d2aafa26be4e926e465267705df383bc1c452

Tx prefix hash: 13a39c6c58c5cd756ef24db4830446fa6885ac43ad8d2f9ecaded7f8d0ef2a39
Tx public key: f8d314a54aac7f38a4adfe5f275d012aaefe5520a86f4b25098cf6e9a4df967b
Timestamp: 1697435183 Timestamp [UCT]: 2023-10-16 05:46:23 Age [y:d:h:m:s]: 01:030:12:38:08
Block: 870684 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 283020 RingCT/type: yes/0
Extra: 01f8d314a54aac7f38a4adfe5f275d012aaefe5520a86f4b25098cf6e9a4df967b02110000000375e3f0e9000000000000000000

1 output(s) for total of 0.799949362000 dcy

stealth address amount amount idx
00: 5c47d352558e3bffbbf7afbb2555f73ef49dae53c6774d8b4dc865cc3e27bcd8 0.799949362000 1325567 of 0

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": 870694, "vin": [ { "gen": { "height": 870684 } } ], "vout": [ { "amount": 799949362, "target": { "key": "5c47d352558e3bffbbf7afbb2555f73ef49dae53c6774d8b4dc865cc3e27bcd8" } } ], "extra": [ 1, 248, 211, 20, 165, 74, 172, 127, 56, 164, 173, 254, 95, 39, 93, 1, 42, 174, 254, 85, 32, 168, 111, 75, 37, 9, 140, 246, 233, 164, 223, 150, 123, 2, 17, 0, 0, 0, 3, 117, 227, 240, 233, 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