Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 780ae462ad6e5fdaaffe39c3bdb7f924f1c872efdb0e2aa7660067aa31b46075

Tx prefix hash: ba1aeb31cbdbf4e8e9d70d367e47f98c85f49ee28db25be1c9afc47c63b5d5ca
Tx public key: 50b22b35d587af0234e54e88f266ca8f22d515e0c1b7938f7a76171d4bdd0a06
Timestamp: 1720968710 Timestamp [UCT]: 2024-07-14 14:51:50 Age [y:d:h:m:s]: 00:223:13:04:19
Block: 1065591 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 159650 RingCT/type: yes/0
Extra: 0150b22b35d587af0234e54e88f266ca8f22d515e0c1b7938f7a76171d4bdd0a0602110000000991e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d34ecafd068f7e0d2b8785e4ab5a06f9b1a59f3bd5269de6c62648345e0667e4 0.600000000000 1536140 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": 1065601, "vin": [ { "gen": { "height": 1065591 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d34ecafd068f7e0d2b8785e4ab5a06f9b1a59f3bd5269de6c62648345e0667e4" } } ], "extra": [ 1, 80, 178, 43, 53, 213, 135, 175, 2, 52, 229, 78, 136, 242, 102, 202, 143, 34, 213, 21, 224, 193, 183, 147, 143, 122, 118, 23, 29, 75, 221, 10, 6, 2, 17, 0, 0, 0, 9, 145, 225, 60, 4, 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