Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1f1f820d06d97b40f0a535cc25242689774e8fe2fd5898381ae489607f883033

Tx prefix hash: c640700df8be052c9161bd83456acdb9de67938a15d8b715c4b08884f34513fb
Tx public key: e8b44dbf299e11c5a990600b70adf4c521e848e13f404a3cae4ae11933191e02
Timestamp: 1741007462 Timestamp [UCT]: 2025-03-03 13:11:02 Age [y:d:h:m:s]: 00:104:05:52:02
Block: 1231256 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 74476 RingCT/type: yes/0
Extra: 01e8b44dbf299e11c5a990600b70adf4c521e848e13f404a3cae4ae11933191e020211000000081f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ddbc96bf16d8f02f61e6c3a87d353942490205b4db22eb62dc98b5d19e6b96bd 0.600000000000 1718163 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": 1231266, "vin": [ { "gen": { "height": 1231256 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ddbc96bf16d8f02f61e6c3a87d353942490205b4db22eb62dc98b5d19e6b96bd" } } ], "extra": [ 1, 232, 180, 77, 191, 41, 158, 17, 197, 169, 144, 96, 11, 112, 173, 244, 197, 33, 232, 72, 225, 63, 64, 74, 60, 174, 74, 225, 25, 51, 25, 30, 2, 2, 17, 0, 0, 0, 8, 31, 10, 83, 235, 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