Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 359beb91cfa7e25a2640d33e51b2e4689542992b85b8ac572124929269501a71

Tx prefix hash: 79d34651d38c0c53ff4ddf4ced758a64f394625c5391a9e8d62c782207b5b6a3
Tx public key: fa33f20046515395b4fb0ea88be092a99c55f75ff912638f2149ad6b06a1f8e5
Timestamp: 1766267460 Timestamp [UCT]: 2025-12-20 21:51:00 Age [y:d:h:m:s]: 00:000:13:56:14
Block: 1438006 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 402 RingCT/type: yes/0
Extra: 01fa33f20046515395b4fb0ea88be092a99c55f75ff912638f2149ad6b06a1f8e50211000000037b1e51ac000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e954c1605e9b00f029c288b4e9a6acc6c152b2a591a2582965d86b7212b0b116 0.600000000000 1926821 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": 1438016, "vin": [ { "gen": { "height": 1438006 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e954c1605e9b00f029c288b4e9a6acc6c152b2a591a2582965d86b7212b0b116" } } ], "extra": [ 1, 250, 51, 242, 0, 70, 81, 83, 149, 180, 251, 14, 168, 139, 224, 146, 169, 156, 85, 247, 95, 249, 18, 99, 143, 33, 73, 173, 107, 6, 161, 248, 229, 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