Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fe24cc0646aa7effd7e4e90d0d79bfaa82e36e8b62ba043150414f759b2abbc7

Tx prefix hash: 814d03b1e660133d389d50f78e6c8e0f07f7fed29d50f0b10333880d48098229
Tx public key: 36af910a00b1f647e2a79b6d9503a5de16fe1335a7064e0f61a23ffd40a3c8dd
Timestamp: 1744733707 Timestamp [UCT]: 2025-04-15 16:15:07 Age [y:d:h:m:s]: 00:254:08:16:34
Block: 1262095 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 179557 RingCT/type: yes/0
Extra: 0136af910a00b1f647e2a79b6d9503a5de16fe1335a7064e0f61a23ffd40a3c8dd021100000004dbb571c1000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bde7f06f0976ece2dd971d5dafd7921433447b8237c34536269103a1d86cfc55 0.600000000000 1749272 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": 1262105, "vin": [ { "gen": { "height": 1262095 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bde7f06f0976ece2dd971d5dafd7921433447b8237c34536269103a1d86cfc55" } } ], "extra": [ 1, 54, 175, 145, 10, 0, 177, 246, 71, 226, 167, 155, 109, 149, 3, 165, 222, 22, 254, 19, 53, 167, 6, 78, 15, 97, 162, 63, 253, 64, 163, 200, 221, 2, 17, 0, 0, 0, 4, 219, 181, 113, 193, 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