Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4c8cf9b7429fe2a63f29723a49e248148cb4795d7916aeff80a9fe06354f7576

Tx prefix hash: a27eca914b24fa5e765c6d77edde70cc485f4aa81aa28cc60e05bc37d85ab488
Tx public key: 6deef9945f424b9b5b0d97f7b3b5150576b3fc06e0cc352f056a1d6f3302b104
Timestamp: 1750702674 Timestamp [UCT]: 2025-06-23 18:17:54 Age [y:d:h:m:s]: 00:150:19:51:16
Block: 1311288 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 105707 RingCT/type: yes/0
Extra: 016deef9945f424b9b5b0d97f7b3b5150576b3fc06e0cc352f056a1d6f3302b10402110000000243846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7ee785ac627b3b06bee22d9af47ac7bb43715d776efbe27807d24a3bf360853e 0.600000000000 1798915 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": 1311298, "vin": [ { "gen": { "height": 1311288 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7ee785ac627b3b06bee22d9af47ac7bb43715d776efbe27807d24a3bf360853e" } } ], "extra": [ 1, 109, 238, 249, 148, 95, 66, 75, 155, 91, 13, 151, 247, 179, 181, 21, 5, 118, 179, 252, 6, 224, 204, 53, 47, 5, 106, 29, 111, 51, 2, 177, 4, 2, 17, 0, 0, 0, 2, 67, 132, 109, 102, 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