Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5ffe2aed3376effe7874aa0ad20d16351be914dd0e7c5ad16e974c4563101fb7

Tx prefix hash: 140003dcd8082f2ddb4497a133301ac3a8af187b421b4b55fb19d3adbf3112d2
Tx public key: 05e4d9fc04fb3dcbfa6a2a40b2b242ef4308a7757105df5fbaf5f59f11d7c5e7
Timestamp: 1658866321 Timestamp [UCT]: 2022-07-26 20:12:01 Age [y:d:h:m:s]: 03:101:10:22:38
Block: 552338 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 852271 RingCT/type: yes/0
Extra: 0105e4d9fc04fb3dcbfa6a2a40b2b242ef4308a7757105df5fbaf5f59f11d7c5e702110000000475e3f0e9000000000000000000

1 output(s) for total of 9.075593772000 dcy

stealth address amount amount idx
00: ee2a907321a59b34a3f3468b4ce1a9154f9761b8a848729b0111388915d6b40c 9.075593772000 984034 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": 552348, "vin": [ { "gen": { "height": 552338 } } ], "vout": [ { "amount": 9075593772, "target": { "key": "ee2a907321a59b34a3f3468b4ce1a9154f9761b8a848729b0111388915d6b40c" } } ], "extra": [ 1, 5, 228, 217, 252, 4, 251, 61, 203, 250, 106, 42, 64, 178, 178, 66, 239, 67, 8, 167, 117, 113, 5, 223, 95, 186, 245, 245, 159, 17, 215, 197, 231, 2, 17, 0, 0, 0, 4, 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