Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fc2eaf8f6eda04f0e887136eceed3be7b2c27490219c219f7212dfa1501c56b8

Tx prefix hash: ebe18050113030f580311de0cb50c1adc315d239592dbfcc692f2708b4e42ef3
Tx public key: a4f275084e5ec8f4673f042269a5ce3158a7db11a15b5dbc51f1b122c5ce76e7
Timestamp: 1729504102 Timestamp [UCT]: 2024-10-21 09:48:22 Age [y:d:h:m:s]: 01:019:16:29:39
Block: 1136313 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 272462 RingCT/type: yes/0
Extra: 01a4f275084e5ec8f4673f042269a5ce3158a7db11a15b5dbc51f1b122c5ce76e7021100000001cab32bb9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: aa12663241703f04ccb12aeb7358571c3cc6a6f3832a68de318bab2b6b4ba944 0.600000000000 1619658 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": 1136323, "vin": [ { "gen": { "height": 1136313 } } ], "vout": [ { "amount": 600000000, "target": { "key": "aa12663241703f04ccb12aeb7358571c3cc6a6f3832a68de318bab2b6b4ba944" } } ], "extra": [ 1, 164, 242, 117, 8, 78, 94, 200, 244, 103, 63, 4, 34, 105, 165, 206, 49, 88, 167, 219, 17, 161, 91, 93, 188, 81, 241, 177, 34, 197, 206, 118, 231, 2, 17, 0, 0, 0, 1, 202, 179, 43, 185, 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