Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 245377a88aca438e802bee0e17d18d47cf1e1d3c2c11c7757c29fcfc0e0c70ef

Tx prefix hash: e5bc4e6d21104ac4b3eb7e700ff9fdc67c6635c98568e42112445f903cde9a0c
Tx public key: b0e70ba6d0438e757dba453bff0e09ba303932e1446b4784576ad3e9bb2b2f7c
Timestamp: 1725633347 Timestamp [UCT]: 2024-09-06 14:35:47 Age [y:d:h:m:s]: 01:064:17:01:52
Block: 1104263 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 304674 RingCT/type: yes/0
Extra: 01b0e70ba6d0438e757dba453bff0e09ba303932e1446b4784576ad3e9bb2b2f7c021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fee36cbf1ca0e18bf27f4b8c055198b262a56721f49384bd2afb3197959b01d2 0.600000000000 1581342 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": 1104273, "vin": [ { "gen": { "height": 1104263 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fee36cbf1ca0e18bf27f4b8c055198b262a56721f49384bd2afb3197959b01d2" } } ], "extra": [ 1, 176, 231, 11, 166, 208, 67, 142, 117, 125, 186, 69, 59, 255, 14, 9, 186, 48, 57, 50, 225, 68, 107, 71, 132, 87, 106, 211, 233, 187, 43, 47, 124, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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