Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1711e1025c76e8b1babfa36cee59bd798b783d3234bbe06dabb3d905d2e5fb3e

Tx prefix hash: 438fd41eb11db554d43d81d29c17695657950b5ff885144a7ef717f7f5f45566
Tx public key: c18b845e1d8a6cb577b4d2ded6da43edc7734015cec5d112ba75d85d0919712f
Timestamp: 1751540816 Timestamp [UCT]: 2025-07-03 11:06:56 Age [y:d:h:m:s]: 00:134:01:31:37
Block: 1317893 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 94058 RingCT/type: yes/0
Extra: 01c18b845e1d8a6cb577b4d2ded6da43edc7734015cec5d112ba75d85d0919712f02110000000325a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3ac95c3ea913ea4dc778fcbfb650dcd9fc969f0893c91acb05a4b68f48a67d0e 0.600000000000 1805564 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": 1317903, "vin": [ { "gen": { "height": 1317893 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3ac95c3ea913ea4dc778fcbfb650dcd9fc969f0893c91acb05a4b68f48a67d0e" } } ], "extra": [ 1, 193, 139, 132, 94, 29, 138, 108, 181, 119, 180, 210, 222, 214, 218, 67, 237, 199, 115, 64, 21, 206, 197, 209, 18, 186, 117, 216, 93, 9, 25, 113, 47, 2, 17, 0, 0, 0, 3, 37, 163, 90, 15, 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