Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 87809b0ae5ffdf4d03a01bfb8394ab542c21bca00558ee846835b1cf0ce10a3e

Tx prefix hash: d763cd2f5ebe544f0c2333da1f402796effb2b00c638cae53876e73afc0fe931
Tx public key: a313a06d4db5a7911169764d503b172dc5b0f882b5e13d10963687b56af2519a
Timestamp: 1704864052 Timestamp [UCT]: 2024-01-10 05:20:52 Age [y:d:h:m:s]: 01:295:13:54:21
Block: 932054 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 470078 RingCT/type: yes/0
Extra: 01a313a06d4db5a7911169764d503b172dc5b0f882b5e13d10963687b56af2519a0211000000039da8e134000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f2310b49b01eb46b82e4b9f831721d45bd0b372fc33e8bd9b4528a26a842e4b0 0.600000000000 1389968 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": 932064, "vin": [ { "gen": { "height": 932054 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f2310b49b01eb46b82e4b9f831721d45bd0b372fc33e8bd9b4528a26a842e4b0" } } ], "extra": [ 1, 163, 19, 160, 109, 77, 181, 167, 145, 17, 105, 118, 77, 80, 59, 23, 45, 197, 176, 248, 130, 181, 225, 61, 16, 150, 54, 135, 181, 106, 242, 81, 154, 2, 17, 0, 0, 0, 3, 157, 168, 225, 52, 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