Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4f99bf0b4385ac17d0ad32126669d1be802f2885879f5232354d252259e4734f

Tx prefix hash: 0865c318b6967d6c4223b30dfae73edd2673b63c0cf4caed2ccbbaa2df6e18f0
Tx public key: 0d6c86e332787c7f7290d77b671e0a69d1efa0c635130217c4cfddbf0717eeea
Timestamp: 1633080767 Timestamp [UCT]: 2021-10-01 09:32:47 Age [y:d:h:m:s]: 03:083:21:08:13
Block: 344380 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 836917 RingCT/type: yes/0
Extra: 010d6c86e332787c7f7290d77b671e0a69d1efa0c635130217c4cfddbf0717eeea0211000000025410958b000000000000000000

1 output(s) for total of 44.353360394000 dcy

stealth address amount amount idx
00: b0c6f889941026e18ec49484c82ab432665293faa194a867b0a787d79ba559c5 44.353360394000 706646 of 0

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": 344390, "vin": [ { "gen": { "height": 344380 } } ], "vout": [ { "amount": 44353360394, "target": { "key": "b0c6f889941026e18ec49484c82ab432665293faa194a867b0a787d79ba559c5" } } ], "extra": [ 1, 13, 108, 134, 227, 50, 120, 124, 127, 114, 144, 215, 123, 103, 30, 10, 105, 209, 239, 160, 198, 53, 19, 2, 23, 196, 207, 221, 191, 7, 23, 238, 234, 2, 17, 0, 0, 0, 2, 84, 16, 149, 139, 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