Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: edc46442828920ea05657f26268061d6d8186e6a5b5c7385590d60bf2f8de0eb

Tx prefix hash: 3434b2d752e9516b8f8c5d441001a7c7f751b630e9345e843587c38fb7313211
Tx public key: 5e5e82a266b94b2a78f83254e13d5f91d494832c3e079bbd8232a64ea88ea2c0
Timestamp: 1766262279 Timestamp [UCT]: 2025-12-20 20:24:39 Age [y:d:h:m:s]: 00:000:16:47:31
Block: 1437958 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 498 RingCT/type: yes/0
Extra: 015e5e82a266b94b2a78f83254e13d5f91d494832c3e079bbd8232a64ea88ea2c00211000000037b1e51ac000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 45af1b6c6e9fc6f9caee05983cb177932ccdc12cfbde8bf82a0a9dfef4f279f3 0.600000000000 1926771 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": 1437968, "vin": [ { "gen": { "height": 1437958 } } ], "vout": [ { "amount": 600000000, "target": { "key": "45af1b6c6e9fc6f9caee05983cb177932ccdc12cfbde8bf82a0a9dfef4f279f3" } } ], "extra": [ 1, 94, 94, 130, 162, 102, 185, 75, 42, 120, 248, 50, 84, 225, 61, 95, 145, 212, 148, 131, 44, 62, 7, 155, 189, 130, 50, 166, 78, 168, 142, 162, 192, 2, 17, 0, 0, 0, 3, 123, 30, 81, 172, 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