Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 67c45afb2cee448a3fdaee214acc46be1c58c423675a0a306b65fbfcc4b3e15e

Tx prefix hash: e2870a02b0e15b5ac7d1a236bfe0a63764a445d7b13aa14c94ca4632143d522b
Tx public key: d426516abc48861e0b1095c3541f1a99dc63350af030b2ce87e07a2636692c6c
Timestamp: 1699139427 Timestamp [UCT]: 2023-11-04 23:10:27 Age [y:d:h:m:s]: 01:065:19:25:56
Block: 884868 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 308198 RingCT/type: yes/0
Extra: 01d426516abc48861e0b1095c3541f1a99dc63350af030b2ce87e07a2636692c6c021100000001faf35c9c000000000000000000

1 output(s) for total of 0.717901723000 dcy

stealth address amount amount idx
00: e7a2afa6fc4d3fd06c5b5538146f81c1dfd2057d5e4c648cde2f4d959ba5b564 0.717901723000 1340617 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": 884878, "vin": [ { "gen": { "height": 884868 } } ], "vout": [ { "amount": 717901723, "target": { "key": "e7a2afa6fc4d3fd06c5b5538146f81c1dfd2057d5e4c648cde2f4d959ba5b564" } } ], "extra": [ 1, 212, 38, 81, 106, 188, 72, 134, 30, 11, 16, 149, 195, 84, 31, 26, 153, 220, 99, 53, 10, 240, 48, 178, 206, 135, 224, 122, 38, 54, 105, 44, 108, 2, 17, 0, 0, 0, 1, 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