Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7cd51373b6b8c1801e8319ece5e02e48589fa07654b9f4bfdda0a91cb54dd613

Tx prefix hash: 13eef45ee015d9b0f99d46588d0e8dac6219afbe4b68b29307ca36eeb51dfbdf
Tx public key: 3dc3a8d099224bf769543d47db75193e12522472d578623b19de0d44a03cf833
Timestamp: 1730708681 Timestamp [UCT]: 2024-11-04 08:24:41 Age [y:d:h:m:s]: 00:144:10:40:36
Block: 1146239 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 103077 RingCT/type: yes/0
Extra: 013dc3a8d099224bf769543d47db75193e12522472d578623b19de0d44a03cf8330211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 425becb47622e6ec8ddb025cf62e595ca4920d3a837a39580c46eb69c6c6a2ae 0.600000000000 1630838 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": 1146249, "vin": [ { "gen": { "height": 1146239 } } ], "vout": [ { "amount": 600000000, "target": { "key": "425becb47622e6ec8ddb025cf62e595ca4920d3a837a39580c46eb69c6c6a2ae" } } ], "extra": [ 1, 61, 195, 168, 208, 153, 34, 75, 247, 105, 84, 61, 71, 219, 117, 25, 62, 18, 82, 36, 114, 213, 120, 98, 59, 25, 222, 13, 68, 160, 60, 248, 51, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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