Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b703b65c04b0909018e1a3f8515eb59bfb737b6f63065867cfc87c469e7234a8

Tx prefix hash: 8aa23e60a3552b0755f264d9e517fd7fa2e9cbfdea6611059ef14496a5d0677c
Tx public key: a364b435d7cd63338dd5957f2976ac9ddb567224b4922f312d11eeacb69c1dc8
Timestamp: 1722183761 Timestamp [UCT]: 2024-07-28 16:22:41 Age [y:d:h:m:s]: 00:166:23:22:14
Block: 1075663 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 119455 RingCT/type: yes/0
Extra: 01a364b435d7cd63338dd5957f2976ac9ddb567224b4922f312d11eeacb69c1dc802110000000be914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c7bff1478f3531f67ac7e875386dc14fc1271fdf8618aa89eee74d8ba6f04957 0.600000000000 1548192 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": 1075673, "vin": [ { "gen": { "height": 1075663 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c7bff1478f3531f67ac7e875386dc14fc1271fdf8618aa89eee74d8ba6f04957" } } ], "extra": [ 1, 163, 100, 180, 53, 215, 205, 99, 51, 141, 213, 149, 127, 41, 118, 172, 157, 219, 86, 114, 36, 180, 146, 47, 49, 45, 17, 238, 172, 182, 156, 29, 200, 2, 17, 0, 0, 0, 11, 233, 20, 221, 21, 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