Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7e53d327b7d72588f87c5b233d78df7c6bf54064d310f103ddd1b9c246797722

Tx prefix hash: 274bb054ec0cbc0b0a1eed1ed949ab13e3f63de52939e641ac72dfc6028a1be4
Tx public key: 3063f711997a74381950dfd92a235b5b32e348c3fa0d4be708ee018a1b2d4462
Timestamp: 1696994556 Timestamp [UCT]: 2023-10-11 03:22:36 Age [y:d:h:m:s]: 01:094:10:27:00
Block: 867034 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 328746 RingCT/type: yes/0
Extra: 013063f711997a74381950dfd92a235b5b32e348c3fa0d4be708ee018a1b2d446202110000000775e3f0e9000000000000000000

1 output(s) for total of 0.822538939000 dcy

stealth address amount amount idx
00: 481bfc6f65e579dfdfff1b569ecfd6fbd8af8edd2e247fa0b33694aa0f39fe54 0.822538939000 1321682 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": 867044, "vin": [ { "gen": { "height": 867034 } } ], "vout": [ { "amount": 822538939, "target": { "key": "481bfc6f65e579dfdfff1b569ecfd6fbd8af8edd2e247fa0b33694aa0f39fe54" } } ], "extra": [ 1, 48, 99, 247, 17, 153, 122, 116, 56, 25, 80, 223, 217, 42, 35, 91, 91, 50, 227, 72, 195, 250, 13, 75, 231, 8, 238, 1, 138, 27, 45, 68, 98, 2, 17, 0, 0, 0, 7, 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