Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 12278edf86454e2b7f68d337b5116873426c1f9c2b4ef42a730d1c6aef32604e

Tx prefix hash: 795cec8874ae31e3f66931b3c409fdde6839e672bfa260ab881448b623eae0a8
Tx public key: c490bec9ed7813a0249ca6b60299c4a7874ba7bc75f7a820cc72f23c2db5d393
Timestamp: 1754661283 Timestamp [UCT]: 2025-08-08 13:54:43 Age [y:d:h:m:s]: 00:097:23:06:50
Block: 1342853 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 69112 RingCT/type: yes/0
Extra: 01c490bec9ed7813a0249ca6b60299c4a7874ba7bc75f7a820cc72f23c2db5d393021100000001ad7948d0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 97f88ffeae904bf6d83a1d0d44cf433b44c32b3a8162c7f39375d527d5b3e083 0.600000000000 1830686 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": 1342863, "vin": [ { "gen": { "height": 1342853 } } ], "vout": [ { "amount": 600000000, "target": { "key": "97f88ffeae904bf6d83a1d0d44cf433b44c32b3a8162c7f39375d527d5b3e083" } } ], "extra": [ 1, 196, 144, 190, 201, 237, 120, 19, 160, 36, 156, 166, 182, 2, 153, 196, 167, 135, 75, 167, 188, 117, 247, 168, 32, 204, 114, 242, 60, 45, 181, 211, 147, 2, 17, 0, 0, 0, 1, 173, 121, 72, 208, 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