Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bae4899f4541c9c132efe510ffd8f73cb5bfd02666b3da78cf54866a318c2ff1

Tx prefix hash: 6e071e3369d36f194aad48f9d4c184d0dff416b590ba0ab45731d6ea2bad0a09
Tx public key: 260041e18d7c69e59e6e1fb78ecbeef4a6426beb3475120973fbc8338c43b768
Timestamp: 1724074205 Timestamp [UCT]: 2024-08-19 13:30:05 Age [y:d:h:m:s]: 01:050:19:30:32
Block: 1091339 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 294718 RingCT/type: yes/0
Extra: 01260041e18d7c69e59e6e1fb78ecbeef4a6426beb3475120973fbc8338c43b768021100000008e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1178c990d947c9c0e08bf4852cd1915f83a9e8b3955b39ab9566b423a86a720b 0.600000000000 1565970 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": 1091349, "vin": [ { "gen": { "height": 1091339 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1178c990d947c9c0e08bf4852cd1915f83a9e8b3955b39ab9566b423a86a720b" } } ], "extra": [ 1, 38, 0, 65, 225, 141, 124, 105, 229, 158, 110, 31, 183, 142, 203, 238, 244, 166, 66, 107, 235, 52, 117, 18, 9, 115, 251, 200, 51, 140, 67, 183, 104, 2, 17, 0, 0, 0, 8, 233, 20, 221, 21, 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