Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 475d4bb8265ea9edffaec3867278f82c27e557677d48fb9a04e0323622b682ee

Tx prefix hash: 35f1ba10e9aa83415163f727f021164d9d14648c54819fa52fc0617f0a62fb11
Tx public key: 4b3cf50cb9c7aae8c79c001730335c7b27ebdcac0352dbbec92596e9f844053a
Timestamp: 1737492381 Timestamp [UCT]: 2025-01-21 20:46:21 Age [y:d:h:m:s]: 00:148:03:41:36
Block: 1202373 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 105635 RingCT/type: yes/0
Extra: 014b3cf50cb9c7aae8c79c001730335c7b27ebdcac0352dbbec92596e9f844053a0211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f1ded5724a73a61ab42ee1ba840db674a5a0a8793e39c344af18ae3b7c9d423a 0.600000000000 1689036 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": 1202383, "vin": [ { "gen": { "height": 1202373 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f1ded5724a73a61ab42ee1ba840db674a5a0a8793e39c344af18ae3b7c9d423a" } } ], "extra": [ 1, 75, 60, 245, 12, 185, 199, 170, 232, 199, 156, 0, 23, 48, 51, 92, 123, 39, 235, 220, 172, 3, 82, 219, 190, 201, 37, 150, 233, 248, 68, 5, 58, 2, 17, 0, 0, 0, 3, 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