Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 86931395ada8d6b3908224f0e40104e549a36213c2dbba27276f7e500fb2ee95

Tx prefix hash: 5ebdae0be9d12353323f105ae77c21fd1ac561ca59bab23d6bea5e2364f9f0b5
Tx public key: 265db3f91a809c7c95b7d2c6187df5373c7b8dcbc47599900f860448e54ad5e7
Timestamp: 1673720342 Timestamp [UCT]: 2023-01-14 18:19:02 Age [y:d:h:m:s]: 01:305:08:55:35
Block: 674733 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 479228 RingCT/type: yes/0
Extra: 01265db3f91a809c7c95b7d2c6187df5373c7b8dcbc47599900f860448e54ad5e7021100000002272bcc39000000000000000000

1 output(s) for total of 3.567216156000 dcy

stealth address amount amount idx
00: e74d2f7f8009a7e7e7d7d242e49c08efd27d62c08d8917e8d7a919018b7ed95d 3.567216156000 1116388 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": 674743, "vin": [ { "gen": { "height": 674733 } } ], "vout": [ { "amount": 3567216156, "target": { "key": "e74d2f7f8009a7e7e7d7d242e49c08efd27d62c08d8917e8d7a919018b7ed95d" } } ], "extra": [ 1, 38, 93, 179, 249, 26, 128, 156, 124, 149, 183, 210, 198, 24, 125, 245, 55, 60, 123, 141, 203, 196, 117, 153, 144, 15, 134, 4, 72, 229, 74, 213, 231, 2, 17, 0, 0, 0, 2, 39, 43, 204, 57, 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