Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c2a7e50b038590be2748d23834a4ed12deebf32df650a1dd593ae69339b2a0aa

Tx prefix hash: 44cca2ae352ed74aa468872eaade376da04f9803d9a19fa4a72715e00a495f84
Tx public key: 4dedcd1459a5cf8f7a7db3d5482b81bad0e639dff0281b34ea1a13e56988afc0
Timestamp: 1762738428 Timestamp [UCT]: 2025-11-10 01:33:48 Age [y:d:h:m:s]: 00:080:11:03:04
Block: 1408755 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 57429 RingCT/type: yes/0
Extra: 014dedcd1459a5cf8f7a7db3d5482b81bad0e639dff0281b34ea1a13e56988afc002110000000201491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f3425f3f31dc22ce00b81c39fd61d3cc57cf3ff5a0a818cd7e5ee80af5dea06c 0.600000000000 1897186 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": 1408765, "vin": [ { "gen": { "height": 1408755 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f3425f3f31dc22ce00b81c39fd61d3cc57cf3ff5a0a818cd7e5ee80af5dea06c" } } ], "extra": [ 1, 77, 237, 205, 20, 89, 165, 207, 143, 122, 125, 179, 213, 72, 43, 129, 186, 208, 230, 57, 223, 240, 40, 27, 52, 234, 26, 19, 229, 105, 136, 175, 192, 2, 17, 0, 0, 0, 2, 1, 73, 31, 136, 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