Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 396074728d97837bdcb44343c4a870efe508ff939c78186a0f52f2a7b06a7ef7

Tx prefix hash: 1313111c9f999faafe1fbf8953ab2867617f2108fda698d41d4d55e571f50d8b
Tx public key: dd196e3698d3bdcd10e184dd57119e450ce9a525a6b500d2b25c28e916c2ec9a
Timestamp: 1737706066 Timestamp [UCT]: 2025-01-24 08:07:46 Age [y:d:h:m:s]: 00:145:04:22:13
Block: 1204153 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 103504 RingCT/type: yes/0
Extra: 01dd196e3698d3bdcd10e184dd57119e450ce9a525a6b500d2b25c28e916c2ec9a0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fba23002f03d3022791d228a7caf5f031d30fb22e0811e1c904f11b296b0b9eb 0.600000000000 1690836 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": 1204163, "vin": [ { "gen": { "height": 1204153 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fba23002f03d3022791d228a7caf5f031d30fb22e0811e1c904f11b296b0b9eb" } } ], "extra": [ 1, 221, 25, 110, 54, 152, 211, 189, 205, 16, 225, 132, 221, 87, 17, 158, 69, 12, 233, 165, 37, 166, 181, 0, 210, 178, 92, 40, 233, 22, 194, 236, 154, 2, 17, 0, 0, 0, 2, 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