Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 20c5d5fc740188447286bc3da32d063a76aa868d362a4016f1fe6826fd53fab3

Tx prefix hash: 16a9c29be3d88ce2b23023be8239eb26e23f786d0f4d482e6916c05609fbebf1
Tx public key: 52cb435e42bd7d7a851e291a1fbd93cae781f6d823ee47a67cfbef09870ae8d5
Timestamp: 1696526725 Timestamp [UCT]: 2023-10-05 17:25:25 Age [y:d:h:m:s]: 01:099:14:36:45
Block: 863149 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 332457 RingCT/type: yes/0
Extra: 0152cb435e42bd7d7a851e291a1fbd93cae781f6d823ee47a67cfbef09870ae8d502110000000275e3f0e9000000000000000000

1 output(s) for total of 0.847284166000 dcy

stealth address amount amount idx
00: 2c0c093115e7b2c843f0fb097f7e687ab77c04cc84fea768c0a82b52c320c2fd 0.847284166000 1317597 of 0

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": 863159, "vin": [ { "gen": { "height": 863149 } } ], "vout": [ { "amount": 847284166, "target": { "key": "2c0c093115e7b2c843f0fb097f7e687ab77c04cc84fea768c0a82b52c320c2fd" } } ], "extra": [ 1, 82, 203, 67, 94, 66, 189, 125, 122, 133, 30, 41, 26, 31, 189, 147, 202, 231, 129, 246, 216, 35, 238, 71, 166, 124, 251, 239, 9, 135, 10, 232, 213, 2, 17, 0, 0, 0, 2, 117, 227, 240, 233, 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