Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fef45080b9d35bb5860674bc34d74b513f8d483a3a6f1a714d2ff38d613487dc

Tx prefix hash: c7e551996eb9018f8a80274d25c1e91ccd30b390cf03b455d43ef7b781c575e2
Tx public key: 7b488e7284ec144f9e15315dc35876b3047c8ff31b505c7a02749a9d21945c6e
Timestamp: 1702062868 Timestamp [UCT]: 2023-12-08 19:14:28 Age [y:d:h:m:s]: 01:190:18:49:04
Block: 908842 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 397439 RingCT/type: yes/0
Extra: 017b488e7284ec144f9e15315dc35876b3047c8ff31b505c7a02749a9d21945c6e02110000000175e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f53f9de47c66841c4cad0add56342bf11e77f38138ed6da7cd914e99a3cdaabd 0.600000000000 1365899 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": 908852, "vin": [ { "gen": { "height": 908842 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f53f9de47c66841c4cad0add56342bf11e77f38138ed6da7cd914e99a3cdaabd" } } ], "extra": [ 1, 123, 72, 142, 114, 132, 236, 20, 79, 158, 21, 49, 93, 195, 88, 118, 179, 4, 124, 143, 243, 27, 80, 92, 122, 2, 116, 154, 157, 33, 148, 92, 110, 2, 17, 0, 0, 0, 1, 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