Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e19fab785b436e0c0f967250ae5795fc014b306d601c31d0eb6a635cd3475222

Tx prefix hash: 08cd731881639e2245decfd4606d2018db9af03e08e60d6b88e8a85aa7e382a2
Tx public key: 24d5efd8fd0e6acd3f6277c9d10011ad5c5d0e29f1a7f501368d1623a74917bf
Timestamp: 1736158840 Timestamp [UCT]: 2025-01-06 10:20:40 Age [y:d:h:m:s]: 00:163:00:46:40
Block: 1191397 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 116218 RingCT/type: yes/0
Extra: 0124d5efd8fd0e6acd3f6277c9d10011ad5c5d0e29f1a7f501368d1623a74917bf0211000000018368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7c4c865115dfb45898cc3864564c44a51052af6325cb14699490802d2076e503 0.600000000000 1677926 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": 1191407, "vin": [ { "gen": { "height": 1191397 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7c4c865115dfb45898cc3864564c44a51052af6325cb14699490802d2076e503" } } ], "extra": [ 1, 36, 213, 239, 216, 253, 14, 106, 205, 63, 98, 119, 201, 209, 0, 17, 173, 92, 93, 14, 41, 241, 167, 245, 1, 54, 141, 22, 35, 167, 73, 23, 191, 2, 17, 0, 0, 0, 1, 131, 104, 38, 109, 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