Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a974237d6e85d84e14f248d6137ef121a53d60dea73b7ecc67da73b24025819c

Tx prefix hash: 6f30d70ee4881059fbac9fd56f9a632230301640b7e67728f37c024d25cabe76
Tx public key: 0c33c10d9ae5dbd832d4a4a326ef17aaf743987afe783dc1b3878a477926b7fa
Timestamp: 1697007433 Timestamp [UCT]: 2023-10-11 06:57:13 Age [y:d:h:m:s]: 01:180:22:42:10
Block: 867140 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 390351 RingCT/type: yes/0
Extra: 010c33c10d9ae5dbd832d4a4a326ef17aaf743987afe783dc1b3878a477926b7fa021100000003faf35c9c000000000000000000

1 output(s) for total of 0.821874005000 dcy

stealth address amount amount idx
00: 8d139039149d3514515de66b6ea106cfbb231556f399eae82d027842c564131a 0.821874005000 1321796 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": 867150, "vin": [ { "gen": { "height": 867140 } } ], "vout": [ { "amount": 821874005, "target": { "key": "8d139039149d3514515de66b6ea106cfbb231556f399eae82d027842c564131a" } } ], "extra": [ 1, 12, 51, 193, 13, 154, 229, 219, 216, 50, 212, 164, 163, 38, 239, 23, 170, 247, 67, 152, 122, 254, 120, 61, 193, 179, 135, 138, 71, 121, 38, 183, 250, 2, 17, 0, 0, 0, 3, 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