Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 70416a502b16449a0d851eb4eeaa83287d4b7f8045493a2df8eb9f270ae7011e

Tx prefix hash: f844a228674698ac75f4572e8e39af0446d803deeefbfa6f4924caa80cf4d5c7
Tx public key: cf35245df51ec26f06e4f42cf5b0aea6f720675a508c3bb0acfc8d4aaa85e8c3
Timestamp: 1759825365 Timestamp [UCT]: 2025-10-07 08:22:45 Age [y:d:h:m:s]: 00:039:20:08:20
Block: 1384605 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 28534 RingCT/type: yes/0
Extra: 01cf35245df51ec26f06e4f42cf5b0aea6f720675a508c3bb0acfc8d4aaa85e8c3021100000003d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8d65be5f762a7e423220b3b6ef9cada94ca3862959535f053e6ee11396a61de9 0.600000000000 1872758 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": 1384615, "vin": [ { "gen": { "height": 1384605 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8d65be5f762a7e423220b3b6ef9cada94ca3862959535f053e6ee11396a61de9" } } ], "extra": [ 1, 207, 53, 36, 93, 245, 30, 194, 111, 6, 228, 244, 44, 245, 176, 174, 166, 247, 32, 103, 90, 80, 140, 59, 176, 172, 252, 141, 74, 170, 133, 232, 195, 2, 17, 0, 0, 0, 3, 216, 231, 210, 65, 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