Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bc20b5b0c7a310201fb2f2079d4d4e0f65788e5c66fa2c705a60e7ada78c1281

Tx prefix hash: 478119f4f5a47f984142b9132657eaf6d75deea54c01634d9ead35eb2750bf6e
Tx public key: aa0f73709119759980ce94515381c0fdc2615f692e8a120e5068da7cdbb7b2c9
Timestamp: 1713149839 Timestamp [UCT]: 2024-04-15 02:57:19 Age [y:d:h:m:s]: 00:336:08:16:00
Block: 1000747 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 240487 RingCT/type: yes/0
Extra: 01aa0f73709119759980ce94515381c0fdc2615f692e8a120e5068da7cdbb7b2c90211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e91ed2b677a24291125b990598c80a884fd49a76a740a55bf5b90f14dc9e7c34 0.600000000000 1461247 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": 1000757, "vin": [ { "gen": { "height": 1000747 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e91ed2b677a24291125b990598c80a884fd49a76a740a55bf5b90f14dc9e7c34" } } ], "extra": [ 1, 170, 15, 115, 112, 145, 25, 117, 153, 128, 206, 148, 81, 83, 129, 192, 253, 194, 97, 95, 105, 46, 138, 18, 14, 80, 104, 218, 124, 219, 183, 178, 201, 2, 17, 0, 0, 0, 4, 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