Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 955c1bc414fd521fe0a9636138d2f416dc3747186f84c667ed9c1010c9f853a9

Tx prefix hash: 91621fa27768bba9c739d501389a18ea8d5126e92e1a7f5c07b911d69489138b
Tx public key: 12bed8f2e4f360ab675083fc5358644c02ed02b20a5ef7d8e8754516a84d3359
Timestamp: 1699853190 Timestamp [UCT]: 2023-11-13 05:26:30 Age [y:d:h:m:s]: 01:111:22:18:24
Block: 890537 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 341151 RingCT/type: yes/0
Extra: 0112bed8f2e4f360ab675083fc5358644c02ed02b20a5ef7d8e8754516a84d3359021100000004faf35c9c000000000000000000

1 output(s) for total of 0.687513510000 dcy

stealth address amount amount idx
00: ff744092a14f02d229373b071d9ccd22874e88069c4fcffa0986a379a3fe5be0 0.687513510000 1346560 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": 890547, "vin": [ { "gen": { "height": 890537 } } ], "vout": [ { "amount": 687513510, "target": { "key": "ff744092a14f02d229373b071d9ccd22874e88069c4fcffa0986a379a3fe5be0" } } ], "extra": [ 1, 18, 190, 216, 242, 228, 243, 96, 171, 103, 80, 131, 252, 83, 88, 100, 76, 2, 237, 2, 178, 10, 94, 247, 216, 232, 117, 69, 22, 168, 77, 51, 89, 2, 17, 0, 0, 0, 4, 250, 243, 92, 156, 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