Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 39d298b3028eba1c644bf21f0b529f9671d59ce389529e880a28464118bbdf32

Tx prefix hash: 15cd34071cd9c495459c8bea2fc473431b1c7253337d0ad18c8e55e51abd372f
Tx public key: 1a4f42e190543b5e4dbf1965681b6a2ea2dcb5368d3367a915974fd1c78b809b
Timestamp: 1709047822 Timestamp [UCT]: 2024-02-27 15:30:22 Age [y:d:h:m:s]: 01:057:07:44:51
Block: 966768 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 301990 RingCT/type: yes/0
Extra: 011a4f42e190543b5e4dbf1965681b6a2ea2dcb5368d3367a915974fd1c78b809b0211000000060011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 71e3cb8baaf0b6fabdc855b2606a6f4babe5a265044cb2eb6d70b84255b45afb 0.600000000000 1426539 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": 966778, "vin": [ { "gen": { "height": 966768 } } ], "vout": [ { "amount": 600000000, "target": { "key": "71e3cb8baaf0b6fabdc855b2606a6f4babe5a265044cb2eb6d70b84255b45afb" } } ], "extra": [ 1, 26, 79, 66, 225, 144, 84, 59, 94, 77, 191, 25, 101, 104, 27, 106, 46, 162, 220, 181, 54, 141, 51, 103, 169, 21, 151, 79, 209, 199, 139, 128, 155, 2, 17, 0, 0, 0, 6, 0, 17, 5, 91, 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