Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7ca7ca12fa3b7151a63afcff31727fd62649de2d0e3507b4db12c2a13c539882

Tx prefix hash: d90ac5bb083894c61e5a78d220ce30bb4a407ba801935be6b6063fe8e0f185ab
Tx public key: 4471a144d9f04bc1a2b762abe3a126ec6c4a9a77c50159b244c0fb289f857e15
Timestamp: 1689524131 Timestamp [UCT]: 2023-07-16 16:15:31 Age [y:d:h:m:s]: 01:267:19:25:05
Block: 805166 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 452517 RingCT/type: yes/0
Extra: 014471a144d9f04bc1a2b762abe3a126ec6c4a9a77c50159b244c0fb289f857e15021100000009faf35c9c000000000000000000

1 output(s) for total of 1.318714933000 dcy

stealth address amount amount idx
00: 2e5ed98b99e8d05ae82d5fff7dd4a9d4d6ed8d8e2c1b3110f683163d748d59fb 1.318714933000 1256385 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": 805176, "vin": [ { "gen": { "height": 805166 } } ], "vout": [ { "amount": 1318714933, "target": { "key": "2e5ed98b99e8d05ae82d5fff7dd4a9d4d6ed8d8e2c1b3110f683163d748d59fb" } } ], "extra": [ 1, 68, 113, 161, 68, 217, 240, 75, 193, 162, 183, 98, 171, 227, 161, 38, 236, 108, 74, 154, 119, 197, 1, 89, 178, 68, 192, 251, 40, 159, 133, 126, 21, 2, 17, 0, 0, 0, 9, 250, 243, 92, 156, 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