Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3093ac4e62506f3924a2857b2836a255dd8ccdcb5c8812b3fd0f0987fb6ea089

Tx prefix hash: c568484f20679e8ad59930bd43458906db733e36c7aee4fd15e97615a5ddb99d
Tx public key: ee1a6281238aadfc6514dd50a6b1b5ab6ff60b49f31d5ac226169f7b6e0e4552
Timestamp: 1760853669 Timestamp [UCT]: 2025-10-19 06:01:09 Age [y:d:h:m:s]: 00:080:06:11:49
Block: 1393150 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 57457 RingCT/type: yes/0
Extra: 01ee1a6281238aadfc6514dd50a6b1b5ab6ff60b49f31d5ac226169f7b6e0e45520211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4104e1104fc2f604859caea8d08885ddfc27ee5374513c11c9a7bf49306d83df 0.600000000000 1881409 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": 1393160, "vin": [ { "gen": { "height": 1393150 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4104e1104fc2f604859caea8d08885ddfc27ee5374513c11c9a7bf49306d83df" } } ], "extra": [ 1, 238, 26, 98, 129, 35, 138, 173, 252, 101, 20, 221, 80, 166, 177, 181, 171, 111, 246, 11, 73, 243, 29, 90, 194, 38, 22, 159, 123, 110, 14, 69, 82, 2, 17, 0, 0, 0, 1, 38, 9, 179, 160, 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