Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ec455613e58928909608b7c0abff04146a45f71ea0d2278f2da5680c10138264

Tx prefix hash: 3d4777c13913185efd235c09146e07c9c0e9aef759f28c89f9abd0774a8f20aa
Tx public key: d79b0f50a7c308389551a68d99a4207f38e2da596e90520ac3e8ed0e0c4c7738
Timestamp: 1759222748 Timestamp [UCT]: 2025-09-30 08:59:08 Age [y:d:h:m:s]: 00:100:10:52:01
Block: 1379609 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 71948 RingCT/type: yes/0
Extra: 01d79b0f50a7c308389551a68d99a4207f38e2da596e90520ac3e8ed0e0c4c773802110000000597baf922000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6bfc719a896a8f9a7d82d2edd085e69e5b75613a55bcce01144808b7b8dd392f 0.600000000000 1867716 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": 1379619, "vin": [ { "gen": { "height": 1379609 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6bfc719a896a8f9a7d82d2edd085e69e5b75613a55bcce01144808b7b8dd392f" } } ], "extra": [ 1, 215, 155, 15, 80, 167, 195, 8, 56, 149, 81, 166, 141, 153, 164, 32, 127, 56, 226, 218, 89, 110, 144, 82, 10, 195, 232, 237, 14, 12, 76, 119, 56, 2, 17, 0, 0, 0, 5, 151, 186, 249, 34, 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