Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1972f23f111c56727e5584a5f1bb0cb4fc862db336bf599e84daec212ebf297e

Tx prefix hash: b3d6803a1c4bf9eecd40245ad8bb5c893f7a12778b6fa083b1ea16447838db0c
Tx public key: d3ae2dc9c3bf26bc766d690afcb21691fb97f8509438e25a5df522c1fab35f9f
Timestamp: 1739713276 Timestamp [UCT]: 2025-02-16 13:41:16 Age [y:d:h:m:s]: 00:320:18:12:51
Block: 1220516 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 227099 RingCT/type: yes/0
Extra: 01d3ae2dc9c3bf26bc766d690afcb21691fb97f8509438e25a5df522c1fab35f9f021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 34992dff950463a062c3cf064ee0fd73cf422a5129b8ecc49dc3790f9c61afd2 0.600000000000 1707357 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": 1220526, "vin": [ { "gen": { "height": 1220516 } } ], "vout": [ { "amount": 600000000, "target": { "key": "34992dff950463a062c3cf064ee0fd73cf422a5129b8ecc49dc3790f9c61afd2" } } ], "extra": [ 1, 211, 174, 45, 201, 195, 191, 38, 188, 118, 109, 105, 10, 252, 178, 22, 145, 251, 151, 248, 80, 148, 56, 226, 90, 93, 245, 34, 193, 250, 179, 95, 159, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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