Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d26635016948fe4e1471d223b0014cde4d60a5834d29da3ded656044ed28b9f0

Tx prefix hash: 91288d0536d314dfab398b88de2787f4827a51c453c73b0e4df2c11661a2b413
Tx public key: 0c9aae7b24e3287f28dbe7e7d42a2ff0700e19ae1658a928bb2e9c6e404de73b
Timestamp: 1765065600 Timestamp [UCT]: 2025-12-07 00:00:00 Age [y:d:h:m:s]: 00:015:04:02:35
Block: 1428036 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 10859 RingCT/type: yes/0
Extra: 010c9aae7b24e3287f28dbe7e7d42a2ff0700e19ae1658a928bb2e9c6e404de73b02110000000270609d03000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: efe2650003339e966ab631473c9ee9a0d48ce8e93b27c15429ef28982aa6bb12 0.600000000000 1916745 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": 1428046, "vin": [ { "gen": { "height": 1428036 } } ], "vout": [ { "amount": 600000000, "target": { "key": "efe2650003339e966ab631473c9ee9a0d48ce8e93b27c15429ef28982aa6bb12" } } ], "extra": [ 1, 12, 154, 174, 123, 36, 227, 40, 127, 40, 219, 231, 231, 212, 42, 47, 240, 112, 14, 25, 174, 22, 88, 169, 40, 187, 46, 156, 110, 64, 77, 231, 59, 2, 17, 0, 0, 0, 2, 112, 96, 157, 3, 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