Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b29d44267e067d684ca5a2c64421c04bfe68a0e5f13ca0595a7b6789bc3b1d6c

Tx prefix hash: 7595ccc542363f66784680dc0f9d4eb92a809b4fafd00be958b7d3a341471b55
Tx public key: f92e2156f0e0668463880cca99f8a2f52e386342f319bd8c0a150049d09771b6
Timestamp: 1749370856 Timestamp [UCT]: 2025-06-08 08:20:56 Age [y:d:h:m:s]: 00:210:01:58:00
Block: 1300505 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 147906 RingCT/type: yes/0
Extra: 01f92e2156f0e0668463880cca99f8a2f52e386342f319bd8c0a150049d09771b602110000000abf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 21afad119edc1d0a5bcd2e6a76a1898a15e26fed33d511a7cf08a78271cc9571 0.600000000000 1788054 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": 1300515, "vin": [ { "gen": { "height": 1300505 } } ], "vout": [ { "amount": 600000000, "target": { "key": "21afad119edc1d0a5bcd2e6a76a1898a15e26fed33d511a7cf08a78271cc9571" } } ], "extra": [ 1, 249, 46, 33, 86, 240, 224, 102, 132, 99, 136, 12, 202, 153, 248, 162, 245, 46, 56, 99, 66, 243, 25, 189, 140, 10, 21, 0, 73, 208, 151, 113, 182, 2, 17, 0, 0, 0, 10, 191, 81, 178, 162, 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