Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 355b132269710a0b7f9422f2efd1dff8844952fda957e01490e69a203a93864b

Tx prefix hash: b326fa0476ac3aee542db1944cde5c8830a5e459ddbe4a3d081e00f50e081d26
Tx public key: 2242bca70c1e77786cbc7f3db81c40bdcfaf072fe9dca0adcb05834b086adcab
Timestamp: 1741572631 Timestamp [UCT]: 2025-03-10 02:10:31 Age [y:d:h:m:s]: 00:256:15:39:42
Block: 1235943 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 181161 RingCT/type: yes/0
Extra: 012242bca70c1e77786cbc7f3db81c40bdcfaf072fe9dca0adcb05834b086adcab0211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e5fd41a85d43071f795125db79f0e6e5e9404dfaae93f8860a965a272b6c7b0a 0.600000000000 1722888 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": 1235953, "vin": [ { "gen": { "height": 1235943 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e5fd41a85d43071f795125db79f0e6e5e9404dfaae93f8860a965a272b6c7b0a" } } ], "extra": [ 1, 34, 66, 188, 167, 12, 30, 119, 120, 108, 188, 127, 61, 184, 28, 64, 189, 207, 175, 7, 47, 233, 220, 160, 173, 203, 5, 131, 75, 8, 106, 220, 171, 2, 17, 0, 0, 0, 4, 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