Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3bbe3b874efa60016292f03dcb09011f48405faa5bc1d403f085130fc6a30163

Tx prefix hash: 8c5f14a1cb07f7260e8fc17d31d10c5a54eabcb16047e766025c34347fdcd59b
Tx public key: 8fa06fe90aae450285b1a81b954744fe30d6e7e22515b7ba2f045af16fb1d0c5
Timestamp: 1728950157 Timestamp [UCT]: 2024-10-14 23:55:57 Age [y:d:h:m:s]: 00:225:06:09:59
Block: 1131758 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 160816 RingCT/type: yes/0
Extra: 018fa06fe90aae450285b1a81b954744fe30d6e7e22515b7ba2f045af16fb1d0c502110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 25bcf4bfebd8abfa30c274af4611f4295ebdbe71f2b88100672065f6543143fa 0.600000000000 1614665 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": 1131768, "vin": [ { "gen": { "height": 1131758 } } ], "vout": [ { "amount": 600000000, "target": { "key": "25bcf4bfebd8abfa30c274af4611f4295ebdbe71f2b88100672065f6543143fa" } } ], "extra": [ 1, 143, 160, 111, 233, 10, 174, 69, 2, 133, 177, 168, 27, 149, 71, 68, 254, 48, 214, 231, 226, 37, 21, 183, 186, 47, 4, 90, 241, 111, 177, 208, 197, 2, 17, 0, 0, 0, 5, 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