Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7e553694e5ee14bb0db657baaf2f3ea632cdfd4a708caaf13819239e86a69f68

Tx prefix hash: 1b5670707046719dca2a2b5a37779247782e5fcc5cd70a4fab1738f1e148ce43
Tx public key: 1b1117d1fb2ad8473c740746f23ce4d9dc96546882a166a9d3c21cdfb5523bdb
Timestamp: 1718217445 Timestamp [UCT]: 2024-06-12 18:37:25 Age [y:d:h:m:s]: 01:201:20:52:15
Block: 1042779 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 402906 RingCT/type: yes/0
Extra: 011b1117d1fb2ad8473c740746f23ce4d9dc96546882a166a9d3c21cdfb5523bdb0211000000018fda9b2d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 90e20692da8b467bdae5339e6d09b36edcba64023c6eb53b389b85bbb4c0b11c 0.600000000000 1511776 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": 1042789, "vin": [ { "gen": { "height": 1042779 } } ], "vout": [ { "amount": 600000000, "target": { "key": "90e20692da8b467bdae5339e6d09b36edcba64023c6eb53b389b85bbb4c0b11c" } } ], "extra": [ 1, 27, 17, 23, 209, 251, 42, 216, 71, 60, 116, 7, 70, 242, 60, 228, 217, 220, 150, 84, 104, 130, 161, 102, 169, 211, 194, 28, 223, 181, 82, 59, 219, 2, 17, 0, 0, 0, 1, 143, 218, 155, 45, 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